Retry on errors from targeting removed shard in add_remove_shards_killop.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • Cluster Scalability 2024-6-10
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When a shard is removed, its ReplicaSetMonitor is removed when the ShardRegistry next refreshes for shards/mongos or when the removal completes on the config server. If a concurrent request tries to use that RSM, it will fail with ShutdownInProgress. add_remove_shards_killop.js uses a $currentOp that may target all shards while concurrently removing shards, and can hit this error, which currently fails the test.

            Assignee:
            Jack Mulrow
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: