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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 1.8.3, 2.0.0
    • Fix Version/s: 2.0.1, 2.1.0
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      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.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-3967 could not initialize cursor across all shards

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-3683 Possible for setShardVersion to never be set on mongod after multiple StaleConfigExceptions due to stale/missing mongod metadata

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              greg_10gen Greg Studer
              Reporter:
              greg_10gen Greg Studer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: