Closed flowinh2o closed 1 year ago
After further investigation it looks the queue uses priorities of compute resources so for this you would just need to put spot first in the list of compute environments and it will be preferred first by the queue.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
IN=n the case when you specify 2 compute environments with both ec2 and ec2 spot is it possible to schedule a job that will only run on spot. Seems like with this module it adds both compute environments to a queue so that it's not possible but maybe I am missing something. Guess I could just run another instance of the module to do that but just seeing if it's possible.