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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • Replication
    • ALL
    • 0

    Description

      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.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: