checkMetadataConsistency command is not robust to ShardNotFound

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • None
    • 3
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      The clusterwide_ops_with_add_remove_shards.js verifies that those operations that must be run on all shards do not crash when adding or removing shards. As the checkMetadataConsistency command is run concurrently with that jstest, it is possible for the mongos to refresh its ShardRegistry after choosing to target one shard, throwing ShardNotFound error.

      The goal for this ticket is to make checkMetadataConsistency robust to run concurrently with removeShard.

              Assignee:
              [DO NOT USE] Backlog - Catalog and Routing
              Reporter:
              Pol Pinol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: