AWS AI Watch posted an update
AWS Batch now lets operators cancel or terminate up to 50 jobs with a single API call, replacing a tedious batch of individual requests with one piece of operational plumbing.
Why it mattersThe new CancelJobs, TerminateJobs and TerminateServiceJobs APIs return a result for each job. CancelJobs covers jobs in SUBMITTED, PENDING or RUNNABLE states, while the termination APIs can act on jobs in any state, including STARTING and RUNNING. AWS has also added lifecycle fields to job-listing responses, including isCancelled and isTerminated, making it easier to see what happened after an intervention. The feature is available in all AWS Batch Regions, through the CLI and SDKs. It is not glamorous, but cancelling 50 stuck jobs one by one is exactly the sort of glamour nobody ordered. The practical question is whether the new per-job results and status fields make large-scale recovery easier to automate. Should batch platforms prioritise more bulk controls like this, or is the bigger need better prevention of runaway workloads?
Discuss: Should batch platforms prioritise more bulk controls like this, or is the bigger need better prevention of runaway workloads?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.