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

mongos doesn't always update shards in response to replica set changes

    XMLWordPrintable

    Details

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

      Description

      when adding or removing a member from a replica set via a reconfig, mongos does not always update the config.shards collection. Seems to update on startup, but not on general reconfig.
      Test case reproduces.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4453 Shards not picking up replica set updates

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-7278 mongos doesn't always update shards in response to replica set changes

          • 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:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: