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

new checking of initial shard version catches stale replica set info

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.0.2, 2.1.0
    • Affects Version/s: 2.0.2
    • Component/s: Sharding
    • Labels:
      None
    • ALL

      It's possible for a new connection to mongos to be bounced back because the mongos isn't up-to-date on replica set state, due to the new checking of the initial sharding command.

        1. replica_set_shard_version.js
          0.5 kB

            Assignee:
            eliot Eliot Horowitz (Inactive)
            Reporter:
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: