Force reconfig that makes current primary unelectable can result in stepdown without taking the global lock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Replication
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a primary learns of a new config via a heartbeat that came in via a force reconfig where it is no longer electable, it will transition itself to SECONDARY, but it does so without holding the global exclusive lock, which is illegal.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: