Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.7.0
Affects Version/s: 2.6.0-rc2
Component/s: Sharding
Labels:
- cap-ticket-needed

Operating System:
ALL
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

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

Assignee:: Randolph Tan
Reporter:: Randolph Tan
Participants:: Githook User, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Mar 28 2014 06:49:17 PM UTC
Updated:: Jul 11 2016 05:17:19 PM UTC
Resolved:: Apr 21 2014 05:55:02 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates