-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS spot failure - custom error message #5240
Comments
Found some of this logic here: nextflow/plugins/nf-amazon/src/main/nextflow/cloud/aws/batch/AwsBatchTaskHandler.groovy Lines 728 to 743 in 12ea4d7
However that's in advance of the error actually triggering, so needs a deeper dive into the code to find the right place for the log message. |
This comment was marked as outdated.
This comment was marked as outdated.
Maybe it could be done check error reason returned by Batch to customise the nextflow error message nextflow/plugins/nf-amazon/src/main/nextflow/cloud/aws/batch/AwsBatchTaskHandler.groovy Lines 271 to 275 in 5a37e61
|
We recently set the default for
aws.batch.maxSpotAttempts
to0
in #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 themaxSpotAttempts
config option so that the user knows how to resolve it?The text was updated successfully, but these errors were encountered: