Bug #14540

[API] Limit number of container lock/unlock cycles

Added by Peter Amstutz 16 days ago. Updated 15 days ago.

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

0%

Estimated time:
Story points:
-

Description

An un-runnable container can get stuck in an infinite loop of lock/unlock cycles (the dispatcher takes it, fails to start it, and the returns it to the queue). It should keep track of the number of times it is locked/unlocked and cancel the container if it exceeds a configured limit.


Related issues

Related to Arvados - Bug #14495: [crunch2] include space required to download/unpack docker image in tmp disk requestNew2018-12-10

History

#1 Updated by Peter Amstutz 16 days ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 15 days ago

  • Description updated (diff)
  • Status changed from In Progress to New

#3 Updated by Peter Amstutz 15 days ago

  • Related to Bug #14495: [crunch2] include space required to download/unpack docker image in tmp disk request added

#4 Updated by Lucas Di Pentima 15 days ago

  • Assigned To set to Lucas Di Pentima

#5 Updated by Lucas Di Pentima 15 days ago

  • Assigned To deleted (Lucas Di Pentima)
  • Target version changed from 2018-12-12 Sprint to To Be Groomed

Also available in: Atom PDF