reset per-connection shard info in mongos when reconnect happens

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ... otherwise mongos takes multiple retries to determine that it really does need to reset the version (because it's a new connection, mongod won't know about the old versions set). If we detect this earlier, it's much less impactful.

      Might be best to roll into other config changes, but wanted to record here for posterity.

            Assignee:
            Unassigned
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: