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

Invalid replset config is accepted by primary but rejected by secondary

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • None
    • 3.4.1
    • Replication
    • None
    • Replication

    Description

      When adding members to a replica set the member being added is checked against the existing members for string equality, but not resolved IP.

      If a member is inadvertently added with a hostname:port that differs from the existing members but resolves to the same IP:port as one of them, the primary will accept the configuration, but the duplicate host will reject it and stop participating in the replica set.

      In a small replica set, this can cause the primary to step down, in which case rs.remove cannot be used to remove the erroneous entry.

      If this can be changed to also resolve the hostname and compare IP:port to ensure no members are duplicated, this issue would be prevented.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            joe.caswell@mongodb.com Joe Caswell
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: