[SERVER-76648] Cleanup and rename check routing table consistency hook Created: 28/Apr/23  Updated: 26/Oct/23

Status: Blocked
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
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-76646 Add teardown checkMetadataConsistency... Backlog
Assigned Teams:
Catalog and Routing
Participants:

 Description   

This hook used to check consistency of the routing table and recently in SERVER-71613 we made so that it is also checking the placement history.

The routing table checks should be covered already by the checkMetadataConsistency hook introduced in PM-3020. To ensure the coverage is exactly the same, we should check that checkMetadataConsistency command is performing the routing table checks also if the primary doesn't have metadata for the specific database.

The goal of this ticket is to:
 - Ensure checkMetadataConsitency and the routing table hook checks are equivalent.
 - Remove the routing table check from the hooks are leave only the historical placement ones.
 - Rename the hook to reflect the fact that is only performing placement history checks.


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