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

Balancer defragmentation policy should be cleared on step down

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.2, 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.3
    • Sharding EMEA 2022-04-18
    • 24

      The in memory state of the defragmentation policy isn't being cleared on step down. We are stopping the balancer threads, which prevents defragmentation from continuing after the node has stepped down, but leaving the in memory state intact can cause defragmentation to resume on re-step-up of an old primary when it should not be resumed (for example, when defragmentation has completed with a different primary). As part of the step down of the balancer, we should clear the _defragmentationStates map in the balancer defragmentation policy.

            Assignee:
            paolo.polato@mongodb.com Paolo Polato
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: