-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This parameter is tricky to take advantage of because it is currently implemented as part of a cursor setting when the cloner is fetching for batches. This means that in order for new values to take effect, the existing cursor must be killed. I think the recipient batch insertion is more impactful than the fetching, so we should consider using this (or a separate parameter) to control how we batch the inserts during cloning and easily change it while cloning is running.
- is related to
-
SERVER-100264 Resharding Natural Order Pipeline Does Not Respect reshardingCollectionClonerBatchSizeInBytes
-
- Closed
-