Step 3: Split the jumbo Chunk. Use either sh.splitAt() or sh.splitFind() to split the jumbo chunk. sh.splitAt( "test.foo", { x: 3 }) MongoDB removes the jumbo flag upon successful split of the chunk. Indivisible Chunks In some instances, MongoDB cannot split the no-longer jumbo chunk, such as a chunk with a range of single shard key value, and the preferred method to clear the flag is not applicable. In such cases, you can clear the flag using the following steps. Important: Only use this method if the preferred method (page 728) is not applicable. Before modifying the config database (page 737), always back up the config database. If you clear the jumbo flag for a chunk that still exceeds the chunk size and/or the document number limit, MongoDB will re-label the chunk as jumbo when MongoDB tries to move the chunk. Step 1: Stop the balancer. Disable the cluster balancer process temporarily, following the steps outlined in Disable the Balancer (page 717). Step 2: Create a backup of config database. Use mongodump against a config server to create a backup of the config database. For example: mongodump --db config --port <config server port> --out <output file> Step 3: Connect to mongos . Connect a mongo shell to a mongos . Step 4: Find the jumbo Chunk. Run sh.status(true) to find the chunk labeled jumbo . sh.status( true ) For example, the following output from sh.status(true) shows that chunk with shard key range { "x" : 2 } -->> { "x" : 3 } is jumbo . --- Sharding Status --- sharding version: { ... } shards: ... databases: ... test.foo shard key: { "x" : 1 } chunks: shard-b 2 shard-b 2 shard-a 2 { "x" : { "$minKey" : 1 } } -->> { "x" : 1 } on : shard-b Timestamp(2, 0) { "x" : 1 } -->> { "x" : 2 } on : shard-a Timestamp(3, 1) { "x" : 2 } -->> { "x" : 4 } on : shard-a Timestamp(2, 2) jumbo { "x" : 4 } -->> { "x" : { "$maxKey" : 1 } } on : shard-b Timestamp(3, 0) MongoDB Documentation, Release 3.0.4 729 10.3. Sharded Cluster Tutorials