[SERVER-11360] Splits can fail if the split point was once a chunk boundary Created: 24/Oct/13  Updated: 11/Jul/16  Resolved: 31/Oct/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.5.3
Fix Version/s: 2.5.4

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

var st = new ShardingTest({ shards: 2, mongos: 2 });
st.stopBalancer();
 
var configDB = st.s.getDB('config');
configDB.adminCommand({ enableSharding: 'test' });
configDB.adminCommand({ shardCollection: 'test.user', key: { x: 1 }});
configDB.adminCommand({ split: 'test.user', middle: { x: 0 }});
 
var configDB2 = st.s1.getDB('config');
configDB2.adminCommand({ mergeChunks: 'test.user', bounds: [{ x: MinKey }, { x: MaxKey }]});
 
// This test will pass if flushRouterConfig is called here.
var res = configDB.adminCommand({ split: 'test.user', middle: { x: 0 }});
assert(res.ok, 'command failed: ' + tojson(res));
 
st.stop();

Participants:

 Comments   
Comment by auto [ 31/Oct/13 ]

Author:

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

Message: SERVER-11360 Splits can fail if the split point was once a chunk boundary

Always refresh first before performing any chunk metadata changing operation on mongos.
Branch: master
https://github.com/mongodb/mongo/commit/b76d47accaefb558d2e0e9175d53e991e74630b2

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