[SERVER-43681] Increase time waiting for ttl thread to run in concurrency suite Created: 27/Sep/19  Updated: 29/Oct/23  Resolved: 03/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: sharding-4.4-stabilization
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-04-06, Sharding 2020-04-20
Participants:
Linked BF Score: 8

 Description   

This time limit should be increased to handle overloaded machines, especially for concurrency suites where the balancer runs very frequently.



 Comments   
Comment by Max Hirschhorn [ 03/Apr/20 ]

The changes in 98e0d30 depend on the TestData.inEvergreen property which was introduced as part of SERVER-46029. If we find ourselves wanting to backport this change to branches earlier than 4.4, then we'll need to introduce the concept of TestData.inEvergreen to those earlier branches, or just change the amount of time we're willing to wait for the TTL monitor to be 10 minutes everywhere.

Comment by Githook User [ 03/Apr/20 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-43681 Wait longer for TTL monitor in indexed_insert_ttl.js.

(cherry picked from commit 98e0d301535330cd57e3a777096b1c2508f1cc79)
Branch: v4.4
https://github.com/mongodb/mongo/commit/d2bbdf3270ef83a26f192f44eb035e3309cba892

Comment by Githook User [ 03/Apr/20 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-43681 Wait longer for TTL monitor in indexed_insert_ttl.js.
Branch: master
https://github.com/mongodb/mongo/commit/98e0d301535330cd57e3a777096b1c2508f1cc79

Generated at Thu Feb 08 05:03:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.