-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
ClusterScalability 2Feb-16Feb
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In ReshardCollectionCoordinator we update the user request object for rewriteCollection provenance with shard key and also save the modified request object as part of the state document. The effect of this is that a successive rewriteCollection command with same user args as before will fail with ConflictingOperationInProgress instead of joining existing operation as it doesn't contain the shard key in its request.
- is caused by
-
SERVER-113427 Improve error handling for when the shard key changes during execution of rewriteCollection
-
- Closed
-
- related to
-
SERVER-127893 Investigate why resharding timeseries abort tests fail with BadValue in sharding_last_lts multiversion context
-
- Needs Scheduling
-