Actions
Idea #4599
closed[Crunch] crunch-job should not retry tasks after its SLURM allocation is revoked
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
-
Start date:
Due date:
Story points:
1.0
Description
When a job is assigned to a single node, and it fails, SLURM revokes the job allocation. See #4410 for example logs. crunch-job correctly detects the node failure, but it then goes to retry the task, which is pointless without the job allocation. The job should fail immediately once the allocation is revoked.
Related issues
Updated by Brett Smith almost 10 years ago
- Subject changed from crunch-job should not retry tasks after its SLURM allocation is revoked to [Crunch] crunch-job should not retry tasks after its SLURM allocation is revoked
- Description updated (diff)
- Category set to Crunch
- Story points set to 1.0
Updated by Tom Clegg over 7 years ago
- Target version deleted (
Arvados Future Sprints)
Actions