-
Notifications
You must be signed in to change notification settings - Fork 683
Manage AWS Batch Unscheduled jobs #5936
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
Manage AWS Batch Unscheduled jobs #5936
Conversation
Signed-off-by: jorgee <[email protected]> AWS unscheduled jobs management Signed-off-by: jorgee <[email protected]>
✅ Deploy Preview for nextflow-docs-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…if-a-compute-env-does-not-meet-the-criteria
Signed-off-by: Paolo Di Tommaso <[email protected]>
Should this be "unscheduled" or "unschedulable" or "misconfigured"? |
plugins/nf-amazon/src/main/nextflow/cloud/aws/config/AwsBatchConfig.groovy
Outdated
Show resolved
Hide resolved
Co-authored-by: Chris Hakkaart <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
I have received some suggestions to include other such as |
Contrary to what I said during our call, let's add |
Co-authored-by: Chris Hakkaart <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]>
…if-a-compute-env-does-not-meet-the-criteria
Signed-off-by: Paolo Di Tommaso <[email protected]>
Adjusted naming, added docs & scope options, added Please have a look and merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs look good
…if-a-compute-env-does-not-meet-the-criteria
Signed-off-by: Ben Sherman <[email protected]>
--------- Signed-off-by: jorgee <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Ben Sherman <[email protected]> Co-authored-by: Paolo Di Tommaso <[email protected]> Co-authored-by: Chris Hakkaart <[email protected]> Co-authored-by: Ben Sherman <[email protected]> Signed-off-by: Dietmar Rieder <[email protected]>
--------- Signed-off-by: jorgee <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Ben Sherman <[email protected]> Co-authored-by: Paolo Di Tommaso <[email protected]> Co-authored-by: Chris Hakkaart <[email protected]> Co-authored-by: Ben Sherman <[email protected]>
--------- Signed-off-by: jorgee <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]> Signed-off-by: Ben Sherman <[email protected]> Co-authored-by: Paolo Di Tommaso <[email protected]> Co-authored-by: Chris Hakkaart <[email protected]> Co-authored-by: Ben Sherman <[email protected]>
close #5897
Detects when a job is in an unscheduled state by checking if the reason status contains
MISCONFIGURED:JOB_RESOURCE_REQUIREMENT
By default, it only prints a warning when the condition is found.
A new
aws.batch.killUnscheduled
flag is added in the configuration to change the default behaviour. Whentrue
, Nextflow kills the unscheduled job and throws a ProcessException with the reason.