-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
2
In SERVER-74251, we introduced a background hook that continuously run the checkMetadataConsistency command in the background for cluster that use the python sharded fixture. This hook does not guarantee that the command will be executed at least once after the test completes.
Thus, the goal of this ticket is to add a new hook that will run during teardown of the test in ShardedCluster python fixture. The difference with respect to the background one is that since we are executing this at the end of the test while the cluster is idle, we can also check the index consistency.
- is depended on by
-
SERVER-76647 Remove UUID consistency check hook
- Blocked
-
SERVER-76648 Cleanup and rename check routing table consistency hook
- Blocked
-
SERVER-76649 Remove index consistency check hook
- Blocked