Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30572

Support configurable 'jumbo' chunk threshold

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible

      Currently if a chunk spans over more than 250,000 documents it will be considered 'jumbo' and the balancer will refuse to move it until it is split into smaller chunks. In the case of bad shard key selection where the key cardinality is too high, jumbo chunks may arise which cannot be split because the entire chunk consists of the same shard key value.

      The hardcoded 250,000 documents limit was included as a precaution against such large chunks taking too long to migrate and causing the donor shard to run out of memory because of accumulation of 'mods'.

      In order to allow users in emergency situations to move jumbo chunks out of shards we should allow this limit to be temporarily increased. If we do this, we should also put a cap on the size of accumulated in-memory mods.

            randolph@mongodb.com Randolph Tan
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            0 Vote for this issue
            8 Start watching this issue