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

Clear the 'jumbo' flag from the chunk document when the chunk is no longer over-sized

    • Type: Icon: New Feature New Feature
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Catalog and Routing

      Currently, if the balancer goes to split a chunk and cannot, the chunk gets marked as 'jumbo', which will prevent the balancer from migrating that chunk and from trying to split it again.

      If in the future, documents are deleted from that shard key range or the cluster's chunksize setting changes, the chunk itself may no longer be 'jumbo', but MongoDB will not clear the 'jumbo' flag from that chunk.

      If you have a system where documents are short-lived (say, one week) and are then removed from the system, this will result in a system with a large number of chunks that are incorrectly marked 'jumbo'. In addition, the number of 'jumbo' chunks will grow over time.

            Assignee:
            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            Reporter:
            william.zola@10gen.com William Zola
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: