Apply the right maxChunkSize value when migrating a chunk

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-02-07
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The chunk size for a specific collection is defined according to the following rules hierarchy:

      1. The collection specific chunk size maxChunkSizeBytes field in config.collection if set
      2. The global chunk size setting in config.settings.chunkSize if set
      3. The default global chunk size setting

      Nevertheless, such criteria aren't respected when a chunk is being migrated out of a shard (more specifically, the wrong value may be taken into consideration when the "end of the catch up phase" condition is evaluated).

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: