nextflow-io / nextflow-io/nextflow
Is AWS Fargate configured to retry after spot interruption?
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
I am using Nextflow with AWS Batch and a Spot Fargate compute environment. I have a job that was terminated with "Your Spot Task was interrupted." but I also see environment variables like "AWS_MAX_ATTEMPTS 5" and "AWS_RETRY_MODE standard". Has retry with Fargate not been implemented or have I missed a configuration somewhere?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file, test, or entry point. Start by checking Nextflow's AWS Batch and Spot Fargate configuration and retry documentation, then determine whether AWS_MAX_ATTEMPTS and AWS_RETRY_MODE apply to interrupted Spot tasks. Done means confirming the supported behavior and identifying any required configuration or implementation gap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100