Drop database coordinator retries indefinetly until stepdowns

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: Backlog
    • Component/s: Sharding
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: