[SERVER-63872] Tighter task and idle timeout Created: 23/Nov/21  Updated: 29/Oct/23  Resolved: 01/Mar/22

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

Type: Task Priority: Blocker - P1
Reporter: Robert Guo (Inactive) Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: dev-prod-qp-idea, dp-qp-stakeholder-request-2022-01, faster-patches
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
Problem/Incident
Related
is related to SERVER-64146 Fix division by zero in timeout calcu... Closed
is related to SERVER-65835 Certain tasks have timeouts set highe... Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2022-03-07
Participants:
Linked BF Score: 83
Story Points: 2

 Description   

See if we can make timeouts tighter globally to avoid fixtures sitting around for too long and generating large logs.

AC: set the task timeout for generated tasks to be some percentage above the targeted runtime. For randomized tests, set the timeout to be some percentage above the max in recent history. Also lower the idle timeout to the target runtime of the longest test, down from 30min as the default.



 Comments   
Comment by Githook User [ 01/Mar/22 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-63872 Tighter task and idle timeouts
Branch: master
https://github.com/mongodb/mongo/commit/22f548f63f83d9254e89498827c7a84392212c53

Comment by Brian Samek [ 09/Feb/22 ]

robert.guo That sounds great, thanks!

Comment by Robert Guo (Inactive) [ 09/Feb/22 ]

brian.samek per David's comment above, we're discussing setting timeouts as part of PM-2684 this week with the project scheduled for this quarter. If we don't get to that, this ticket will be a P1

Comment by Brian Samek [ 09/Feb/22 ]

robert.guo - Do you think this is likely to be scheduled?

Comment by David Bradford (Inactive) [ 25/Jan/22 ]

We might be able to improve this via PM-2684. For generated tasks, we already set custom timeouts based on the historic runtimes of the tests in the task. As part of PM-2684, we would likely move that to a more common path that could be used by non-generated tasks as well (that project would also allow more tasks to be generated).

There are some areas where this won't help. If there are tests with no history, or tests are randomly named so that they don't build up history (like fuzzers). We would likely need another approach for these type of tasks.

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