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

Make replica set state transition smoother on the C++ driver

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.3.1
    • Internal Client, Sharding
    • None
    • ALL

    Description

      Whenever the configuration of a replica set changes, not all instances (whether they are kept by a thread servicing a client connection, idle in the pool or active) of the connections would know about this event. This can cause some unintuitive behaviors especially when mongos tries to use a very old replica set connection and gets a "not master" error.

      Proposed fix would be to make the replica set connection retry (meaning, re-evaluate the target host) when it gets the "not master" error (and perhaps consider for some class of errors as well) for the first time.

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: