-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It appears that the moveChunk command can return a write conflict error rather than retrying it internally.
- causes
-
SERVER-138096 Handle write conflicts in create_indexes_return_on_start.js sharding setup operations
-
- Closed
-
- is depended on by
-
SERVER-138181 Remove write conflict handling for create_indexes_return_on_start.js sharding setup operations
-
- Blocked
-
- is related to
-
SERVER-138176 Write conflict can escape addShard command
-
- Needs Scheduling
-
-
SERVER-138177 Write conflict can escape shardCollection command
-
- Needs Scheduling
-
-
SERVER-138178 Write conflict can escape split command
-
- Needs Scheduling
-