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

The BalancerCommandsScheduler needs to persist on disk information on moveChunk commands under execution.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2021-09-20, Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18

    Description

      The collection chunks defragmentation algorithm info involves the submission of moveChunk commands from the ConfigServer through BalancerCommandsScheduler.

      The involved shards may require tens of seconds to complete such operation, during which an election of a new ConfigServer primary may occur: the new primary will have to resume the defragmentation algorithm from a stable state - meaning that no new commands may be issued as long as all the moveChunk operations launched by its predecessor have completed.

      As a preliminary task to support such initialisation logic, information on moveChunk commands under execution need to be persisted on disk and kept up to date.

      Attachments

        Activity

          People

            paolo.polato@mongodb.com Paolo Polato
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: