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

Recipient config validation may leave ReplicationCoordinator in a bad state

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Serverless
    • ALL

    Description

      When a node receives a heartbeat containing a recipient config, it first checks if the config is valid. A few lines later we print out a warning and bail early if the validation produces a non-OK status. The replication coordinator state when performing this validation is kConfigHBReconfiguring, and bailing early in this case fails to transition the state back to a state which could accept future reconfigs. The effect is that once a node fails this validation, it can no longer receive additional reconfigs in the future.

      Attachments

        Activity

          People

            backlog-server-serverless [DO NOT USE] Backlog - Server Serverless (Inactive)
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: