Bug #4427
closed
[Workbench] Each active job/pipeline on the dashboard should show how many worker nodes are allocated to it.
Added by Ward Vandewege over 9 years ago.
Updated 18 days ago.
Description
"Local jobs" will be easy to spot: they will have no worker nodes are allocated.
This answers the question "are these jobs actually consuming compute node resources?"
Distinguishing local jobs from batch jobs later, after they have completed, is a separate story.
- Subject changed from [Workbench] Jobs and pipelines that are running in local mode show show up on the dashboard page under 'currently running jobs/pipelines' to [Workbench] Jobs and pipelines that are running in local mode should be marked as such on the dashboard page under 'currently running jobs/pipelines' (and elsewhere in Workbench)
- Description updated (diff)
- Category set to Workbench
- Subject changed from [Workbench] Jobs and pipelines that are running in local mode should be marked as such on the dashboard page under 'currently running jobs/pipelines' (and elsewhere in Workbench) to [Workbench] Each active job/pipeline on the dashboard should show how many worker nodes are allocated to it.
- Description updated (diff)
- Target version deleted (
Arvados Future Sprints)
- Target version set to Future
- Status changed from New to Closed
- Release deleted (
60)
- Target version deleted (
Future)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by