Project

General

Profile

Actions

Bug #15707

closed

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

Added by Ward Vandewege over 4 years ago. Updated about 4 years ago.

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

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
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 open1 closed)

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

Actions
Actions #1

Updated by Ward Vandewege over 4 years ago

  • Description updated (diff)
Actions #2

Updated by Tom Clegg over 4 years ago

  • Subject changed from [a-d-c] considers containers 'on hold' as queued to [arvados-dispatch-cloud] should not include "on hold" containers in "queued" metrics
  • Description updated (diff)
  • Target version set to Arvados Future Sprints
Actions #3

Updated by Tom Clegg over 4 years ago

  • Status changed from New to In Progress
  • Assigned To set to Tom Clegg
  • Target version changed from Arvados Future Sprints to 2019-10-23 Sprint
Actions #5

Updated by Eric Biagiotti over 4 years ago

Actions #6

Updated by Tom Clegg over 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
Actions #7

Updated by Peter Amstutz about 4 years ago

  • Release set to 22
Actions

Also available in: Atom PDF