There is really no way for FireWorks to terminate your job midway. You will need to interact with your queue scheduler to kill the job (e.g., qdel or scancel, etc). If you are using “reservation mode”, FireWorks can help you get the queue id for a particular job (“lpad get_qid” command) to help you know which job to cancel but that’s about it.
There are also ways you could write your task to check for things like disk space while copying and terminate if the disk is getting full, but you’d have to set that up in advance. This could be done with a custom Firework or using the BackgroundTask functionality. These would be pre-coded checks, not an all of a sudden “kill my job” request.
On Fri, Feb 9, 2018 at 12:01 PM, Michelle Brenner [email protected] wrote:
When I have a task that needs to be terminated I can change the firework status. However, that does not stop the task on the firework from finishing whatever it was doing. Say the scenario is the task is copying files from one drive to another and the second drive is filling up. I want to stop it before it does. The only way I know of is manually killing the task runner. Is there anyway to say stop all tasks on this firework immediately?
You received this message because you are subscribed to the Google Groups “fireworkflows” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fireworkflows.
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/64de621f-bcca-4cb2-ac6e-75809d6923fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.