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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0.7
    • Fix Version/s: None
    • Component/s: Sharding
    • Operating System:
      ALL

      Description

      When running rs.reconfig() to remove a node from a replica set, the config servers do not reflect the updated connection string. That is, config.shards is not updated.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-3333 mongos sometimes does not update config server with RS changes

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

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

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-7291 MongoS can hang after replica set reconfiguration due to writeback listener command sequence

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

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              benjamin.becker Ben Becker
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: