-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.6, 3.5.10
-
Component/s: Sharding
-
Sharding EMEA
-
ALL
The moveChunk command crosses from mongos > config server > donor shard > recipient shard. Any maxTimeMS information gets lost after the config server.
Currently it is not safe to always observe maxTimeMS or interrupt on the donor shard, because the migration critical section is not prepared to handle it and may result in fassert.
This ticket is to figure out our story with moveChunk interruptability and deadline observance. Once it has been fixed, the disabled test below needs to be re-enabled.
- depends on
-
SERVER-45338 Make moveChunk robust to maxTimeMS expiring
- Closed
- duplicates
-
SERVER-48153 Chunk migration can still be running even after the moveChunk command fails with maxTimeMS timeout
- Backlog
- related to
-
SERVER-72329 Complete TODO listed in SERVER-30179
- Blocked
-
SERVER-48153 Chunk migration can still be running even after the moveChunk command fails with maxTimeMS timeout
- Backlog