Hello Jean Paul,
Thanks a lot for all this info!
Few questions/notes:
"- The first one is to use the max_load attribute and put a max load value on Machine1 and low value on Machine2
When Machine1 goes down, it will be automatically set offline and all your jobs will be running on Machine2"
Does setting a high max load value on Machine1 and a low one on Machine2 guarantee priority job submission on all executions to Machine1, unless that machine is down, or are there still chances that jobs could submit to Machine2?
"- The second option is to use a machine chooser script to get rid of the virtual machine definition
machine_chooser"
VERY interesting, was not aware of that functionality. But, I'm unsure how do we pass the machine name to the scheduler log. Is there a variable that the script should populate once it completes it selection? Tried to find example of such a script, not really fruitful.
"- The third option is to put some logic in your fail-over environment or in the scripts used to start the second node in a cluster environment to ensure that the first node is offline when you start the fail-over node (Machine2)."
Not really an option in my situation.
Thank you very much!
Have a great day,
Tom