-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.0.14, 3.2.11
-
Component/s: Sharding
-
None
-
Sharding
-
ALL
-
(copied to CRM)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
In MongoDB 3.2 and earlier the shards take Global S lock during migration of chunks out of a shard. This happens both in the beginning and at completion.
Given that migrations are per collection, we should be able to only use collection X or S lock instead.
This problem does not apply to version 3.4 where the chunk migration code was changed significantly.