In the critical section of a migration we check to make sure a majority of secondaries have received the migration writes. If the secondaries fall behind at that point, it's possible for the migration to be stuck in the critical section for a long time (we timeout after 5 minutes). During that time, however, the whole cluster can become unusable as setShardVersion commands will block until the shard is out of the critical section.
- is depended on by
-
SERVER-7500 Set socket timeout on connection used to run _recvChunkCommit to greater than the internal timeout of the command
- Closed
- is related to
-
SERVER-7034 timeouts for all connections in migrate critical section
- Closed
-
SERVER-7493 Possible for read starvation to cause migration to get stuck in critical section
- Closed
- related to
-
SERVER-7298 thousands of "waiting till out of critical section"
- Closed