Bug #4256

[API] Jobs that sit in the front of the queue for a long time without running should be cancelled

Added by Peter Amstutz almost 5 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
1.0

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.

History

#1 Updated by Peter Amstutz almost 5 years ago

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"
}

#2 Updated by Ward Vandewege over 4 years ago

  • 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

#3 Updated by Peter Amstutz over 4 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints

#4 Updated by Peter Amstutz over 4 years ago

  • 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.

#5 Updated by Peter Amstutz over 4 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints

#6 Updated by Ward Vandewege over 4 years ago

  • Story points set to 1.0

Also available in: Atom PDF