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

add_remove_shards_killop.js is not compatible with config transition suites

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc12
    • Affects Version/s: 8.1.0-rc0, 8.0.0-rc12
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-07-08
    • 200

      add_remove_shards_killop.js continuously execute addShard and removeShard and randomly kills some of them. This test is currently running in some suites that have a hook running transitionToDedicated and transitionFromDedicated in the background, so the following scenario could happen:

      1. transitionToDedicated starts draining the config.system.sessions collection
      2. The destination shard of the migration is removed and added with the same id

      This makes the dropCollection in addShard to drop the recently migrated collection, causing a consistency issue. This is not a problem that users would encounter, it is the result of rapidly removing and adding the same shard with the same id, so we should blacklist the test from suites that perform add/remove shard in the background.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: