search

broadinstitute / cromwell

Scientific workflow engine designed for simplicity & scalability. Trivially transition between one off use cases to massive scale production environments
http://cromwell.readthedocs.io/
BSD 3-Clause "New" or "Revised" License
972 stars 353 forks source link

restarted jobs use wrong backend #4215

Open notestaff opened 5 years ago

notestaff commented 5 years ago

My cromwell config has two backends, local and AWSBATCH; local is the default. I submitted a workflow with workflow options setting backend to AWSBATCH. After quitting cromwell and later restarting, it is trying to resubmit jobs to the local engine, and of course failing.

Horneth commented 5 years ago

it is trying to resubmit jobs to the local engine

Do you mean jobs that were running when you stopped Cromwell were "restarted" on the local backend ? Or new downstream jobs for the same workflow were then submitted to the local backend ? Or both ?

I imagine you did not change your configuration in between the stop/start ?

notestaff commented 5 years ago

The former. I didn’t change the config file, but I did override its default engine when submitting the jobs before the restart.