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

Don't assume old primary is still primary when no nodes are returning isMaster

    XMLWordPrintableJSON

Details

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

    Description

      If a shard's primary steps down, but the mongos can't connect to the new primary, the mongos continues thinking that the old primary is still the master. This will cause it to send setShardVersion commands to the former primary, which will fail and be retried many times.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: