[SERVER-74534] checkMetadataConsistency not working with co-located configsvr Created: 02/Mar/23  Updated: 17/Apr/23  Resolved: 17/Apr/23

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

Type: Bug Priority: Major - P3
Reporter: Pol Pinol Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-74445 Cluster checkMetadataConsistency fail... Closed
Related
related to SERVER-74251 Introduce checkMetadataConsistency te... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:

 Description   

Current implementation of the command checkMetadataConsistency in cluster level mode is not working in:

  • concurrency_sharded_with_balancer_and_catalog_shard
  • concurrency_sharded_with_catalog_shard

These suite are the ones in which we use co-located configsvr. This means that a shard is both a shard and the config server at the same time. Thus, when the mongos process the checkMetadataConsistency it sends both the:

  • _shardsvrCheckMetadataConsistency
  • _configsvrCheckClusterMetadataConsistency

To the same node that is a catalog shard (both shard and confisvr at the same time).

For the moment, we have disabled the CheckMetadataConsistency hook to run for those suites.


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