[SERVER-75495] Ensure that 0 inconsistencies are found after dropping databases in check_metadata_consistency.js Created: 30/Mar/23  Updated: 29/Oct/23  Resolved: 03/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
Participants:

 Description   

Add a checkMetadataConsistency run after dropping databases as this part of the test does in sharding/check_metadata_consistency.js (i.e HERE, HERE, ...).

In addition, when an assert of the inconsistencies found fails, we should print them to facilitate an easy debug.



 Comments   
Comment by Githook User [ 03/Apr/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-75495 Ensure that 0 inconsistencies are found after dropping databases in check_metadata_consistency.js
Branch: master
https://github.com/mongodb/mongo/commit/c1ae966737faef128234ee239e913f558f9e3c3a

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