[SERVER-81017] Add a new check to the `checkMetadataConsistency` command to ensure that if a collection exists in the sharding catalog, it is present in at least one shard Created: 13/Sep/23 Updated: 07/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Silvia Surroca |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: | |
| Story Points: | 2 |
| Description |
|
In the checkMetadataConsistency command, if we find a collection registered in the sharding catalog that is not present locally in the shard, we are going to ignore it. This logic is applied to all participant shards. The goal of this ticket is to add a new metadata check to ensure that, if a collection exists in the sharding catalog, it will be present in at least one shard. |