-
Type: Bug
-
Resolution: Incomplete
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.6.9
-
Component/s: Sharding
-
Labels:None
-
ALL
-
We have an existing collection with a small number of records that will soon see a lot more. It was already sharded on a hashed application guid. Our goal is equivalent to a pre-split of an empty collection; we want to match the number of chunks to the new expected use of this collection.
We're using a splitting routine that lists the chunks in the config server, and for each chunk, calls split with the bounds. We were able to split this collection until we hit a point where it seems that there's an empty chunk which we can't split.
2015-07-20T16:50:21.009+0000 [conn121938] splitting chunk [{ guid: 4611686018427387902 },{ guid: 4625894529193607559 }) in collection game_production.objects on shard game-mongodb-cluster-1-data-6 2015-07-20T16:50:21.009+0000 [conn121938] want to split chunk, but can't find split point chunk ns: game_production.objects, shard: game-mongodb-cluster-1-data-6:game-mongodb-cluster-1-data-6/game-mongodb-cluster-1-data-6-1:27018,game-mongodb-cluster-1-data-6-2:27018,game-mongodb-cluster-1-data-6-3:27018, lastmod: 8|434||000000000000000000000000, min: { guid: 4611686018427387902 }, max: { guid: 4625894529193607559 } got: <empty>
The only correlated log we can find across all mongo processes is this from the primary in that shard:
2015-07-20T15:58:49.756+0000 [conn240524] request split points lookup for chunk game_production.objects { : 4611686018427387902 } -->> { : 4625894529193607559 } 2015-07-20T15:58:49.756+0000 [conn240524] splitVector doing another cycle because of force, keyCount now: 0 2015-07-20T15:58:49.756+0000 [conn240524] warning: chunk is larger than 17984 bytes because of key { guid: 4613685088596591651 }
Our expectation is that, even if the chunk is empty, the key range can be split without a problem.