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

Replica seed list in the config servers can be left outdated

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.2.0-rc0
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      We never check whether ConfigServer::replicaSetChange was able to successfully update the shard list with the newly updated seed list and this could leave the seed list in config servers to be outdated for a long time since this only gets triggered once ReplicaSetMonitor sees that the local replica set host list it has is different from isMaster.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: