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

Prevent early destruction of sharding DDL coordinators

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • Backlog
    • None
    • Fully Compatible
    • ALL
    • Sharding 2021-04-05, Sharding EMEA 2021-05-03
    • 138

    Description

      Currently there is no guarantee that the ShardingDDLCoordinator will emplace their completion promises before their destruction. In fact it is possible that we loose all the references to a coordinator, in fact if a stepdown/shutdown happens between:

      1. By removing its stored document (the POS will remove its reference from the active instance map)
      2. By interrupting the command from which the coordinator was originated.

      We will loose all the reference to the coordinator that will be destructed without having the chance to set its completion promise.

      The proposed solution here is to move the removal of the coordinator document to the onCompletion task of the ShardingDDLCoordinator, so that ti will be done in the same future chain task.

      Attachments

        Activity

          People

            tommaso.tocci@mongodb.com Tommaso Tocci
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: