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

ShardRegistry in config servers can keep invalid entries after it rolls back until next reload

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v4.0
    • Sharding 2018-12-17

    Description

      When config server rollbacks data its ShardRegistry that is used for targeting gets out of sync. Instead, it should immediately call reload to avoid the inconsistent state.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39498 ShardRegistry reload inside onReplicationRollback can get stuck

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32375 Config metadata commands should not use readConcern majority

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33256 shardCollection gets DuplicateKeyError if it retries inserting to config.collections after failing to wait for writeConcern

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

          Activity

            People

              misha.tyulenev@mongodb.com Misha Tyulenev
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: