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

Add better retry logic to mongos on doing updates to config data

    XMLWordPrintableJSON

Details

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

    Description

      Turn off balancing
      Bring down one config server
      Bring that config server back up
      Then try to turn balancing back on. The write to the config database will fail with a transport error indicating the mongos can't reach the config server that was just down. If you try the same write again, however, the write goes through b/c the mongos has reconnected with the config server. There should be retry logic in the mongos to handle this so that the mongos will automatically reconnect to the newly restarted config server and try the update again.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: