Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
ALL
Description
While we reload shard information before running the balancer, we don't do the same for auto-migrates, and the logic for the target shard is different from the balancer policy.
There's also a secondary race condition in that it's possible for shard status to change after shard info reload and before the migration is triggered, but this is a much rarer event and will generally be caught while waiting for draining.
Attachments
Issue Links
- duplicates
-
SERVER-14506 special top chunk logic can move max chunk to a shard with incompatible tag
-
- Closed
-