Story #4599

[Crunch] crunch-job should not retry tasks after its SLURM allocation is revoked

Added by Brett Smith about 3 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
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

Related to Arvados - Bug #4410: [Crunch] crunch-job should exit tempfail when a SLURM node failsResolved2014-11-04

History

#1 Updated by Brett Smith about 3 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

#2 Updated by Tom Clegg 9 months ago

  • Status changed from New to Closed

#3 Updated by Tom Clegg 9 months ago

  • Target version deleted (Arvados Future Sprints)

Also available in: Atom PDF