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

    XMLWordPrintable

Details

    • New Feature
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Sharding
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding-emea Backlog - Sharding EMEA
              william.zola@10gen.com William Zola
              Votes:
              2 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated: