[SERVER-73034] Investigate if checkMetadataConsistency command must skip jstests Created: 19/Jan/23  Updated: 29/Oct/23  Resolved: 21/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: Pol Pinol
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-17, Sharding EMEA 2023-05-01
Participants:

 Description   

SERVER-71823 introduced the basic structure of new checkMetadataConsistency command.

As part of that ticket, the new command was skipped from the jstests:

  • jstests/core/views/views_all_commands.js
  • jstests/replsets/all_commands_downgrading_to_upgraded.js
  • jstests/replsets/db_reads_while_recovering_all_commands.js
  • jstests/sharding/database_versioning_all_commands.js
  • jstests/sharding/libs/last_lts_mongos_commands.js
  • jstests/sharding/read_write_concern_defaults_application.js
  • jstests/sharding/safe_secondary_reads_drop_recreate.js
  • jstests/sharding/safe_secondary_reads_single_migration_suspend_range_deletion.js
  • jstests/sharding/safe_secondary_reads_single_migration_waitForDelete.js

We should investigate if checkMetadataConsistency command must continue skipping those jstests.



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

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-73034 Enable command validations for checkMetadataConsistency command, resolving previous skip behavior
Branch: master
https://github.com/mongodb/mongo/commit/5b85f803cb5c206b9722125877d42835aafd0eeb

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