[SERVER-78117] checkMetadataConsistency command is not robust to ShardNotFound Created: 15/Jun/23  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Pol Pinol Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-77509 CheckMetadataConsistencyInBackground ... Closed
Assigned Teams:
Catalog and Routing
Operating System: ALL
Participants:

 Description   

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.


Generated at Thu Feb 08 06:37:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.