Project

General

Profile

Actions
Copy link

Bug #15707

closed

[arvados-dispatch-cloud] should not include "on hold" containers in "queued" metrics

Added by Ward Vandewege about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Tom Clegg
Category:
-
Target version:
2019-10-23 Sprint
Start date:
10/21/2019
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
Arvados 2.0 - Early 2020
Release relationship:
Auto

Description

On qr1hi, we currently have 26 queued containers according to a-d-c. None are running and the situation hasn't changed in many hours.

One example is https://workbench.qr1hi.arvadosapi.com/containers/qr1hi-dz642-ga16kq3tdga8nnn, which is listed as 'on hold' aka priority=0. That is because the matching container request is cancelled (https://workbench.qr1hi.arvadosapi.com/container_requests/qr1hi-xvhdp-t2l3czj8z3c49fj).

a-d-c should not report containers in that state as queued.

Subtasks 1 (0 open — 1 closed)

Task #15738: Review 15707-dispatch-onhold-metricsResolvedTom Clegg10/21/2019

Actions
Actions
Copy link

Also available in: Atom PDF