Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.7.3
-
ALL
Description
Prior to v2.7, mongos can move the top chunk (with maxKey) to a different shard as part of an optimization when performing auto-split. This stopped working on v2.7
Attachments
Issue Links
- is depended on by
-
SERVER-14506 special top chunk logic can move max chunk to a shard with incompatible tag
-
- Closed
-
- is related to
-
SERVER-13402 bulk insert can result in too large chunks
-
- Closed
-