[SERVER-50641] Add more aggressive timeouts to commit queue tasks Created: 31/Aug/20  Updated: 29/Oct/23  Resolved: 02/Sep/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: David Bradford (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: DAG 2020-09-07
Participants:
Story Points: 1

 Description   

There are occasionally issues where the tasks in the commit queue appear to hang. Since the default timeouts are around 2 hours, this can cause large back ups in the queue. We could add more aggressive timeouts to the tasks in the queue so that they timeout much earlier. The lint tasks already do this and timeout around 40 minutes.

We should look at the historic runtimes of the tasks to pick appropriate timeouts.


As a server engineer,
I want hung commit queue tasks to time out earlier,
So that the commit queue does not get blocked for a long period of time waiting for a task that is just going to timeout anyway.


AC:

  • All tasks in the commit-queue have a timeout of under 1 hour.


 Comments   
Comment by Githook User [ 02/Sep/20 ]

Author:

{'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}

Message: SERVER-50641: Set more aggressive timeouts for commit-queue tasks
Branch: master
https://github.com/mongodb/mongo/commit/7acaf5a8297d3f3b3d7bca656ec6f46419014122

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