In this try-catch block used by the CheckMetadataConsistencyHookInBackground hook, we are swallowing any metadata inconsistency error found by the checkMetadataConsistency command. This means that even though the inconsistencies will be found and logged, they won't result in a test failure that triggers a BF investigation.
- derives
-
SERVER-130695 Re-enable InconsistentShardCatalogCollectionMetadata check in CheckMetadataConsistencyInBackground hook
-
- In Progress
-
-
SERVER-130694 Re-enable MalformedTimeseriesBucketsCollection check in CheckMetadataConsistencyInBackground hook
-
- Needs Scheduling
-
- is caused by
-
SERVER-112933 Escape CheckMetadataConsistency hook assertion from running in sharded clusters
-
- Closed
-
-
SERVER-94979 Make CheckMetadataConsistency hook don't rely on the discovery topology helpers
-
- Closed
-
- is related to
-
SERVER-90889 Check timeseries collections throught the checkMetadataConsistency command
-
- Closed
-