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

do not perform UUID check against a shard's config cache in the sharding_csrs_continuous_config_stepdown_WT suite

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.0
    • 3.6.3, 3.7.3
    • Sharding
    • None
    • Fully Compatible
    • v3.6
    • Sharding 2018-02-12, Sharding 2018-02-26
    • 0

    Description

      In the stepdown suite, if the config server primary steps down during shardCollection just before sending setShardVersion to the primary shard, the primary shard may never receive setShardVersion, therefore never refresh its cache for the collection, and so not have an entry in its cache for the collection.

      This causes the UUID check that compares the UUID on the config server with the UUID in a shard's cache to fail.

      We should not perform this check in the stepdown suite, until it is guaranteed that a shard refreshes its cache after shardCollection.

      Attachments

        Issue Links

          Activity

            People

              esha.maharishi@mongodb.com Esha Maharishi
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: