[SERVER-76646] Add teardown checkMetadataConsistency hook Created: 28/Apr/23  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-76647 Remove UUID consistency check hook Blocked
is depended on by SERVER-76648 Cleanup and rename check routing tabl... Blocked
is depended on by SERVER-76649 Remove index consistency check hook Blocked
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

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.


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