Actions
Bug #4427
open
[Workbench] Each active job/pipeline on the dashboard should show how many worker nodes are allocated to it.
Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
1.0
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.
Updated by Tom Clegg about 10 years ago
- 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)
Updated by Tom Clegg about 10 years ago
- Description updated (diff)
- Category set to Workbench
Updated by Tom Clegg about 10 years ago
- 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)
Updated by Ward Vandewege over 3 years ago
- Target version deleted (
Arvados Future Sprints)
Actions