"MongoDB" chunk too big to move solution

Source: Internet
Author: User

When the amount of data in some blocks is particularly large, when a large block is formed, the balancer cannot split the data block and cannot move the block. With the MONGDB 3.2 version, the solution is as follows:


1. First Close balancer

Sh.stopbalancer ()

2. Query large blocks

Use Configdb.chunks.find ({jumbo:true})


3. Splitting a large block

Sh.splitat ("Db.collection", {shardkye: "Split Critical Value"})


4. Manual nudge block (optional step)

Sh.movechunk ("Db.collection", {shardkey: "Shardkey Block"}, "target Shard ID to be moved");


5. Restart Balancer

Sh.startbalancer ()


This article is from the architect's path blog, so be sure to keep this source http://lizhuquan0769.blog.51cto.com/2591147/1767568

"MongoDB" chunk too big to move solution

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.