Bug #4256
closed
[API] Jobs that sit in the front of the queue for a long time without running should be cancelled
Added by Peter Amstutz over 9 years ago.
Updated over 4 years ago.
Description
If a job sits at the front of the queue without running for some period of time, it should be automatically cancelled on the assumption that it is probably unrunnable. The timeout should be configurable, maybe 24 hours.
These jobs have been in the queue for two weeks at the time of this writing:
qr1hi-8i9sb-abi1i4mhj1brv9p
qr1hi-8i9sb-h4thmuuhl2xyzpl
Trying to cancel the jobs results in fiddlesticks:
{
":errors":[
"#<ArvadosModel::PermissionDeniedError: ArvadosModel::PermissionDeniedError>"
],
":error_token":"1413571611+e9ddfe45"
}
- Subject changed from Job has been queued for two weeks and can't be cancelled to [API] Job has been queued for two weeks and can't be cancelled
- Target version changed from Bug Triage to Arvados Future Sprints
- Subject changed from [API] Job has been queued for two weeks and can't be cancelled to [API] Jobs that sit in the front of the queue for a long time without running should be cancelled
- Description updated (diff)
- Target version changed from Arvados Future Sprints to Bug Triage
The fiddlesticks error is covered in #4273. This ticket is now specifically about jobs sitting in the queue for a long time and never running.
- Target version changed from Bug Triage to Arvados Future Sprints
- Target version deleted (
Arvados Future Sprints)
- Status changed from New to Closed
Also available in: Atom
PDF
Updated by 
Updated by