[SERVER-86158] change fail point used in TTL operation metrics tests Created: 02/Feb/24  Updated: 08/Feb/24  Resolved: 08/Feb/24

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.3, v7.0
Sprint: Execution Team 2024-02-19
Participants:
Linked BF Score: 0

 Description   

ttl_operation_metrics_multi_dbs.js may fail due to unexpected metrics collected on the second DB if the TTL monitor is not able to run two passes over the TTL index in db2.coll. This may happen on a slow machine and the TTL index is not registered in time for the first pass to run.

The test currently uses a fail point that pauses TTL operation in the middle of a TTL pass. We could consider using a different existing fail point that allows us to pause between passes so that we can get a complete view of the catalog when the test resumes TTL operation.



 Comments   
Comment by Githook User [ 07/Feb/24 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@users.noreply.github.com', 'username': 'benety'}

Message: SERVER-86158 fix TTL operation metrics tests to accommodate slow deletes (#18750)

GitOrigin-RevId: b5347cb0a1057502f79b65a158fb53d6bb095ed1
Branch: master
https://github.com/mongodb/mongo/commit/2cf2693a7846bb49b9e819c8be4863e096c85ebe

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