-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
Following the introduction of authoritative checks for database metadata within checkMetadataConsistency, we identified the potential benefits of running these checks on secondary nodes.
This ticket is intended to track the investigation into whether we can run a subset of database metadata validations from checkMetadataConsistency on secondary nodes.
One suggestion is to introduce a new optional parameter, which would be disabled by default. When enabled, this parameter would allow for the execution of these secondary validations.
- depends on
-
SERVER-99805 checkMetadataConsistency to check against durable shard metadata
-
- Closed
-
-
SERVER-99806 checkMetadataConsistency to check against temporary DSS
-
- Closed
-