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

Drop database coordinator retries indefinetly until stepdowns

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • Backlog
    • None
    • Sharding

    Description

      Currently the drop database coordinator is only partially resilient to CSRS/participant stepdowns or network partitions, in fact currently we rely on the retry logic of some other component such as the runCommandWithFixedRetryAttempts function that is retrying just 3 times. The goal of this ticket is to make the drop database coordinator retries all its phases indefinitely until a stepdown happen.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-54945 Make drop database resilient to stepdowns on sharded cluster

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-56211 Complete TODO listed in SERVER-55396

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-56495 Complete TODO listed in SERVER-55396

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              marcos.grillo@mongodb.com Marcos José Grillo Ramirez
              tommaso.tocci@mongodb.com Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: