-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:One 2.2 Shard Server (shard0001)
One 2.4 Shard Server (shard0000)
One 2.4 MongoS/Config Server
db.test2.drop()
for(i=-5000;i<5000;i++){db.test2.insert({x:i})}
db.test2.ensureIndex( { x : 1 });
db.test2.ensureIndex( { x : "hashed" });
sh.enableSharding("test");
sh.shardCollection("test.test2", {x:"hashed"});
sh.moveChunk("test.test2", { x: MinKey}, "shard0001");
sleep(1000);
sh.splitAt("test.test2", { x: 0});
sleep(1000);
sh.moveChunk("test.test2", { x: MinKey}, "shard0000");
db.test2.find({x:100})One 2.2 Shard Server (shard0001) One 2.4 Shard Server (shard0000) One 2.4 MongoS/Config Server db.test2.drop() for(i=-5000;i<5000;i++){db.test2.insert({x:i})} db.test2.ensureIndex( { x : 1 }); db.test2.ensureIndex( { x : "hashed" }); sh.enableSharding("test"); sh.shardCollection("test.test2", {x:"hashed"}); sh.moveChunk("test.test2", { x: MinKey}, "shard0001"); sleep(1000); sh.splitAt("test.test2", { x: 0}); sleep(1000); sh.moveChunk("test.test2", { x: MinKey}, "shard0000"); db.test2.find({x:100})
-
ALL
If you run a sharded cluster with one shard running 2.2 and one shard running 2.4 you can end up with invalid chunk migrations.
This happens as the 2.2 node incorrectly processes the moveChunk command on the hashed shard key and does not correctly find all documents which should be migrated.
This can potentially leave whole chunks orphaned.
- duplicates
-
-
- Closed
-
- is related to
-
SERVER-9906 Protecting against version skew between mongos and mongods
-
- Closed
-
- related to
-
-
- Closed
-