Project

General

Profile

Actions

Bug #19624

closed

Better documentation of interaction between priority 0 and container state

Added by Peter Amstutz about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
Story points:
0.5
Release relationship:
Auto

Description

current comment at https://doc.arvados.org/main/api/methods/container_requests.html is

Clients are expected to submit container requests with zero priority in order to preview the container that will be used to satisfy it. Priority can be null if and only if state!=“Committed”. See below for more details .

"below" is

Priority 0 means no container should run on behalf of this request, and containers already running will be terminated (setting container priority to 0 is the cancel operation.)

Priority 1 is the lowest priority.

Priority 1000 is the highest priority.

Let's add a diagram showing the possible states and state changes.


Files

7da8a84dd.png (72.9 KB) 7da8a84dd.png Tom Clegg, 01/30/2023 08:44 PM
32ec983b8.png (55.9 KB) 32ec983b8.png Tom Clegg, 01/30/2023 10:47 PM
PXL_20230131_144714264.jpg (1.31 MB) PXL_20230131_144714264.jpg Brett Smith, 01/31/2023 02:52 PM
d2c770ed6.png (66.8 KB) d2c770ed6.png Tom Clegg, 01/31/2023 09:29 PM
e6da4efc4.png (69.7 KB) e6da4efc4.png Tom Clegg, 02/01/2023 07:16 PM
ContainerRequestLifecycle.dot (2.76 KB) ContainerRequestLifecycle.dot Brett Smith, 02/01/2023 09:14 PM
ContainerRequestLifecycle.dot.svg (11.8 KB) ContainerRequestLifecycle.dot.svg Brett Smith, 02/01/2023 09:14 PM

Subtasks 1 (0 open1 closed)

Task #19643: Review 19624-priority-docResolvedTom Clegg02/02/2023Actions
Actions

Also available in: Atom PDF