[SERVER-14667] mongos does not move top chunk after auto-split Created: 23/Jul/14  Updated: 21/Oct/14  Resolved: 06/Aug/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.7.3
Fix Version/s: 2.7.5

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: cap-ticket-needed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-14506 special top chunk logic can move max ... Closed
Related
is related to SERVER-13402 bulk insert can result in too large c... Closed
Tested
Operating System: ALL
Participants:

 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



 Comments   
Comment by Githook User [ 06/Aug/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-14667 mongos does not move top chunk after auto-split

Added more comment to test
Branch: master
https://github.com/mongodb/mongo/commit/d1ea3910fc9acd03a4964a66ff9b27ef1112a5c5

Comment by Githook User [ 06/Aug/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-14667 mongos does not move top chunk after auto-split
Branch: master
https://github.com/mongodb/mongo/commit/94d9e73102a3e7b623d57635573066fcb5b0be97

Generated at Thu Feb 08 03:35:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.