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

Balancer defragmentation test should check remaining chunks at the end of tests

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.3.0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21

    Description

      Currently, the test for defragmentation (balancer_defragmentation_merge_chunks.js) is testing that defragmentation has happened solely based on the number of chunks. This is not a very robust or thorough and should be replaced by checks on the chunks existing after the tests run.

      After phase 1, we should ensure that there are no sequential chunks on the same shard. In phase 2, we can check that there are no small chunks left who could be merged with another chunk. And for phase 3, we should check that there are no chunks over the configured maxChunkSize.

      Attachments

        Activity

          People

            allison.easton@mongodb.com Allison Easton
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: