-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding
-
ALL
If a shard primary purposely shuts itself down during a migration (usually because of a problem communicating with the config servers while in the critical section), we should release all distributed locks while shutting down so that future migrations aren't blocked after the shard recovers (from RS failover and/or by manually bringing the primary back online).
- is duplicated by
-
SERVER-24431 collection lock not release for mongod failure
- Closed