DOCSP-45041-adding-rolling-limitation-to-behavior (#462)

* DOCSP-45041-adding-rolling-limitation-to-behavior

* DOCSP-45041-adding-rolling-limitation-to-behavior

* DOCSP-45041 default index link

Author: ltran-mdb2

source/includes/rolling-build-limitation.rst

@@ -0,0 +1,10 @@
+``mongosync`` does not support :ref:`rolling index builds
+<index-building-replica-sets>` during migration. To avoid building
+indexes in a rolling fashion during migration, use one of the following
+methods to ensure that your destination indexes match your source
+indexes:
+
+- Build the index on the source before migration.
+- Build the index on the source during migration with a :ref:`default
+  index build <index-creation-background>`. 
+- Build the index on the destination after migration. 

source/reference/limitations.txt

@@ -175,13 +175,4 @@ System Collections
 Rolling Index Builds
 --------------------
 
-``mongosync`` does not support :ref:`rolling index builds
-<index-building-replica-sets>` during migration. To avoid building
-indexes in a rolling fashion during migration, use one of the following
-methods to ensure that your destination indexes match your source
-indexes:
-
-- Build the index on the source before migration.
-- Build the index on the source during migration with a non-rolling
-  index build. 
-- Build the index on the destination after migration. 
+.. include:: /includes/rolling-build-limitation.rst

source/reference/mongosync/mongosync-behavior.txt

@@ -208,6 +208,11 @@ synchronization. The original values are restored during the commit process.
      - In some cases, synchronization may create dummy indexes on the 
        destination to support writes on sharded or collated collections. 
 
+Rolling Index Builds
+~~~~~~~~~~~~~~~~~~~~
+
+.. include:: /includes/rolling-build-limitation.rst
+
 Destination Clusters
 --------------------