Feature #15087

[Workbench] Show number of queued containers on dashboard (instead of busy/idle nodes)

Added by Tom Clegg about 1 month ago. Updated about 1 month ago.

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

0%

Estimated time:
Story points:
1.0

Description

Background: Currently Workbench1 has "busy/idle nodes" counters on the dashboard, but they stop working or disappear if the deprecated crunch1 services are not running. This issue suggests a low-cost way to maintain some semblance of an "is anything happening?" indicator on Workbench after migrating to crunch2.

Feature: On the Workbench1 dashboard, if crunch2 is enabled, show
  • the number of containers (visible to the current user) that have state=Queued and priority>0
  • the number of containers (visible to the current user) that have state=Locked or Running
  • time since the earliest start time of any running container (visible to the current user)
  • how long the oldest visible queued container has been waiting
Benefits:
  • Easy to implement1 in Workbench in a way that works with all dispatch setups
  • Corresponds to reasonable user expectations ("it shouldn't take 2 hours to start a container")
Shortcomings:
  • "Lots of other users' containers are queued ahead of yours" looks identical to "nothing is running at all" (assuming user is not admin)
  • "Cluster is at capacity, with long-running containers" looks identical to "cluster is unable to run anything at all"
  • Doesn't take advantage of the metrics we are (or could be) tracking in arvados-dispatch-cloud, like recent queued-to-starting delays and # busy/idle/booting cloud instances.

1 Assuming we aren't too picky about the definition of "oldest" -- currently we don't record how long a container has been ready to run, only when it was created (since when it might have spent lots of time having priority=0) and when it was last modified (at which point it might have merely raised its priority long after it was ready to run)


Related issues

Related to Arvados - Story #15133: Remove crunch v1 (jobs api)New

History

#1 Updated by Tom Clegg about 1 month ago

  • Description updated (diff)

#2 Updated by Tom Clegg about 1 month ago

  • Description updated (diff)

#3 Updated by Tom Clegg about 1 month ago

  • Target version changed from To Be Groomed to Arvados Future Sprints
  • Story points set to 1.0

#4 Updated by Peter Amstutz 20 days ago

  • Related to Story #15133: Remove crunch v1 (jobs api) added

Also available in: Atom PDF