Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
Catalog and Routing
-
3
Description
This means that running a new migration immediately after a previous one failed with timeout can fail because there's a conflicting chunk migration in progress.
Attachments
Issue Links
- is depended on by
-
SERVER-72329 Complete TODO listed in SERVER-30179
-
- Blocked
-
- is duplicated by
-
SERVER-30179 moveChunk doesn't obey maxTimeMS consistently
-
- Closed
-
- is related to
-
SERVER-30179 moveChunk doesn't obey maxTimeMS consistently
-
- Closed
-
-
SERVER-47003 MaxTimeMSExceeded on _configsvrMoveChunk can lead to blocking future migrations for that chunk
-
- Closed
-
-
SERVER-48699 MaxTimeMS may expire in range_deleter_interacts_correctly_with_refine_shard_key.js test before _configsvrMoveChunk command started
-
- Closed
-