new checking of initial shard version catches stale replica set info

XMLWordPrintableJSON

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

      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 Horowitz (Inactive)
              Reporter:
              Greg Studer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: