nextflow-io / nextflow-io/nextflow
AWS spot failure - custom error message
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
We recently set the default for aws.batch.maxSpotAttempts to 0 in https://github.com/nextflow-io/nextflow/pull/5215 to avoid unexpected costs in cloud.
This is good, but it means we go back to the state we had before this feature was implemented, which is people's Nextflow pipeline runs crashing with the extremely unhelpful message that AWS returns. From memory this has no mention spot reclamation or anything, and is not at all intuitive for new users.
In order for aws.batch.maxSpotAttempts to work, I assume that Nextflow must be capturing these spot reclamation errors already. Even if we're not retrying, can we use that opportunity to print a more helpful error message to the Nextflow log explaining what has happened, and pointing to the maxSpotAttempts config option so that the user knows how to resolve it?
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
Start by tracing the AWS Batch handling associated with the aws.batch.maxSpotAttempts configuration option and determine where spot reclamation errors are captured. Confirm the current AWS error reaches the Nextflow log, then make the completed behavior a helpful message explaining spot reclamation and pointing users to maxSpotAttempts for resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, groovy
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100