Project

General

Profile

Feature #11336

reduce default timeouts

Added by Greg Farnum over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Core
Target version:
-
Start date:
04/06/2015
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:

Description

Right now the timeouts for a teuthology job are quite long. Historically this was because the timeout period included the attempt to lock nodes, which could take a while.

Now, though, we have a "waiting" state!

So instead of an extremely large timeout (Zack said he thought it was 36 hours) we can have a shorter one (12 hours, maybe?) that doesn't begin until we exit the waiting state.

That would help with situations like #11314 where a broken task (that fails and hangs without noticing) will lock up all the machines in a job until the full teuthology timeout has passed.

History

#1 Updated by Zack Cerza over 4 years ago

  • Tracker changed from Fix to Feature

Just a note that, as proposed, this would require moderate changes to teuthology and also paddles.

Also available in: Atom PDF