Controlled primary step-down with no loss of write availability

XMLWordPrintableJSON

    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Stepping down a primary, to allow another replica member to become primary, incurs a brief period where no writes can be accepted. This can lead to application errors when not handled correctly and is a deterrent for some when considering machine maintenance or database upgrade.

      Please allow for a controlled step down where there is no loss of write availability.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              James Wahlin
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: