Loading...

XML

Word

Printable

JSON

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

Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

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

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

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

Created:: Jul 23 2014 10:31:41 PM UTC
Updated:: Oct 21 2014 10:10:22 PM UTC
Resolved:: Aug 06 2014 06:12:05 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates