Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.6.0-rc2
-
ALL
Description
Mongos performs auto-split checking after batch writes have been applied. However, the auto-split logic currently only limits the maximum split points to 2. So if you have a 1MB chunkSize and jam the batch with 16MB worth of documents, the auto split logic will only split the chunks into 3, instead of 16.
Attachments
Issue Links
- is duplicated by
-
SERVER-5066 mongos splits should back off when metadata lock is taken and splitting $max or $min
-
- Closed
-
-
SERVER-12581 mapReduce sharded output replace does not fully split
-
- Closed
-
- related to
-
SERVER-14667 mongos does not move top chunk after auto-split
-
- Closed
-