History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3664
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: Benoit Maury-Bouet
Votes: 3
Watchers: 0

If you were logged in you would be able to see more operations.

Introduce a pulse/ping notion for timeouts

Created: 10/Feb/21 09:33 AM   Updated: 10/Feb/21 01:13 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
Dear all,
It would be nice if we could have another settings for timeouts like this:
Don't timeout if process is still sending data (stdout/stderr)
Which could also go with a "kill process if still running for XXX" (true timeout in this case)

Is it clear ?

 All   Comments   Work Log   Change History      Sort Order:
Benoit Maury-Bouet [10/Feb/21 01:00 PM]
So to give a little more detail

If I set 30 min timeout on a process that doesn't have this option check, as before step will be timedout if not finished under 30 min
If I set 30 min timeout on a process WITH the option enabled, the timeout will only start as soon as no outputs are made, and be resert if you is made, if none are received after 30 min => timeout
If I set 30 min timeout on a process WITH the option enabled and a "kill process if still running for" is set for 2h, then even if there was outputs received => timeout after 2h of the job running

Robin Shen [10/Feb/21 01:13 PM]
Thanks. This is very clear.