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

reset per-connection shard info in mongos when reconnect happens

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      ... 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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: