-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
It appears that the addShard command can return a write conflict error rather than retrying it internally.
- causes
-
SERVER-138121 Retry addShard on write conflicts during ShardingTest initialization
-
- Closed
-
- is depended on by
-
SERVER-138180 Remove addShard write conflict retry in ShardingTest initialization
-
- Blocked
-
- related to
-
SERVER-138177 Write conflict can escape shardCollection command
-
- Needs Scheduling
-
-
SERVER-138178 Write conflict can escape split command
-
- Needs Scheduling
-
-
SERVER-138179 Write conflict can escape moveChunk command
-
- Needs Scheduling
-