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

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.0
    • Fix Version/s: 3.6.3, 3.7.3
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2018-02-12, Sharding 2018-02-26
    • Linked BF Score:
      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

              Assignee:
              esha.maharishi Esha Maharishi
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: