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

Only mark chunks as jumbo if split fails because the chunk is too large

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Sharding 2019-04-22

    Description

      Currently, if the balancer tries to move a chunk and fails because it is too large, it will then attempt to split that chunk. If the split fails for any reason we mark the chunk as jumbo. This means that things like transient network errors and the config servers not being available for writes can lead to chunks being marked as jumbo incorrectly. We should only mark the chunk as jumbo if the reason it failed to be split is that it is in fact jumbo.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-13806 Need better detection and reporting of the existence of jumbo chunks

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-13024 Clear the 'jumbo' flag from the chunk document when the chunk is no longer over-sized

          • Major - P3 - Major loss of function.
          • Needs Scheduling

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: