Possible for setShardVersion to never be set on mongod after multiple StaleConfigExceptions due to reset metadata

XMLWordPrintableJSON

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

      If metadata is reset in the shard connection info on the mongod for a connection, subsequent requests to that namespace will fail repeatedly since the mongos will not detect the metadata needs to be refreshed.

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

                Created:
                Updated:
                Resolved: