[SERVER-83995] Disable secondary index consistency check for sensitive tests Created: 07/Dec/23  Updated: 26/Jan/24  Resolved: 10/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Jess Balint Assignee: Moustafa Maher
Resolution: Fixed Votes: 0
Labels: pm-855-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-85782 Disable index consistency check for t... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-12-25, Repl 2024-01-08, Repl 2024-01-22
Participants:
Linked BF Score: 0

 Description   

Some tests, such as `operation_latency_histogram.js` assert on command counters. SERVER-80339 introduces dbCheck calls for secondary indexes and this requires issuing a `listIndexes` command. This command runs out of band from the test and makes it impossible to reliably test the command counters. We should disable the secondary index checks for the db under test either by hardcoding the database name in the test or, if the passthrough is in the same process, the test can provide the db for which the check should be disabled.



 Comments   
Comment by Githook User [ 06/Jan/24 ]

Author:

{'name': 'Moustafa Maher', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}

Message: SERVER-83995 Disable secondary index consistency check for sensitive tests (#17678)

GitOrigin-RevId: ec58b7b40510e14a171c27a66f56f2001ef6d957
Branch: master
https://github.com/mongodb/mongo/commit/8b770700462342516c3fc6515738731400aa8cfd

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