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

Make new replication code resilient to members being removed from the replset config

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.7.8
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL

      Currently the _slaveInfoMap in ReplicationCoordinatorImpl is never cleared out, which can cause an fassert in prepareReplSetUpdatePositionCommand

      {handshakes}

      if a node in the map can't be found in the config.

      Simplest way to deal with this seems to be to remove entries from the map on reconfig if the memberID can no longer be found in the new config

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: