-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.0.4
-
Component/s: Sharding
-
None
-
Environment:Linux (virtual) #28-Ubuntu SMP Fri Jan 27 18:22:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric
Total of four ec2 instances with the following configuration:
server 1 running mongos
server 2 running mongod, config server (shard1)
server 3 running mongod, config server (shard2)
server 4 running mongod, config server (shard3)
Using the mongodb-10gen repo from apt-get.
Linux (virtual) #28-Ubuntu SMP Fri Jan 27 18:22:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric Total of four ec2 instances with the following configuration: server 1 running mongos server 2 running mongod, config server (shard1) server 3 running mongod, config server (shard2) server 4 running mongod, config server (shard3) Using the mongodb-10gen repo from apt-get.
-
OS X
Issue is while trying to pre-split a chunk on a sharded collection using the 'find', 'to' split options. Using the 'middle' option works as shown below:
MongoDB shell version: 2.0.6
connecting to: test
mongos> db.createCollection('test');
mongos> use admin
switched to db admin
mongos> db.runCommand(
);
{ "ok" : 1 }mongos> db.runCommand({'shardcollection': 'test.test', key: {'key1': 1, 'key2': 1}});
{ "collectionsharded" : "test.test", "ok" : 1 }mongos> db.runCommand({split: 'test.test', find:
{ 'key1': 1, 'key2': 1 }, to: { 'key1': 6, 'key2': 6 }});
{
"assertion" : "splitVector command (median key) failed:
",
"assertionCode" : 13503,
"errmsg" : "db assertion failure",
"ok" : 0
}
mongos> db.runCommand({split: 'test.test', find:
, to:
{ 'key1': 5, 'key2': 5 }, maxChunkSize: 16});
{
"assertion" : "splitVector command (median key) failed:
",
"assertionCode" : 13503,
"errmsg" : "db assertion failure",
"ok" : 0
}
mongos> db.runCommand({split: 'test.test', middle: { 'key1': 3, 'key2': 3 }});
I've also tried increasing and decreasing the chunk size from the config db with no changes to the above error message.