Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13907

Investigate changes in SERVER-48450: Fail reconfigs that contain non-voting nodes from another replica set

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • 4.9.0
    • manual, Server
    • None

    Description

      Description

      Downstream Change Summary

      When executing a quorum check, the node will now wait for all heartbeat requests to be received or time out. Previously, the node would only wait for a majority of voting nodes before continuing with the quorum check.

      Description of Linked Ticket

      Currently the quorum check doesn't require checking non-voting nodes, so even though they'll error, that won't prevent the reconfig from succeeding. Currently If a reconfig adds a non-voting node that is already initialized in another RS, that node will go into the "DOWN" state since it will reject every heartbeat made to it. Failing the reconfig would be a better user experience.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          Activity

            People

              naomi.pentrel@mongodb.com Naomi Pentrel (Inactive)
              backlog-server-pm Backlog - Core Eng Program Management Team
              Naomi Pentrel Naomi Pentrel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                1 year, 11 weeks, 6 days ago