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.