Parallel is ignoring the (--sshlogin) attribute order when used with (--keep-order ) option

[Mehta, Cyrus]

Here is my example where I request that the job runs on LNXVP1262 first before starting on LNXVP1251. 

 

date ; echo 'hostname;date;sleep 10;date' | parallel --no-run-if-empty --will-cite --onall --keep-order --joblog ${runDir}/jobLog.txt --results ${runDir}/resultsDir --jobs 1 --sshlogin LNXVP1262,LNXVP1251  

 

Results:

 

Wed Sep  6 17:35:01 EDT 2023

LNXVP1251

Wed Sep  6 17:35:02 EDT 2023

Wed Sep  6 17:35:12 EDT 2023

LNXVP1262

Wed Sep  6 17:35:13 EDT 2023

Wed Sep  6 17:35:23 EDT 2023

 

How can I make sure the results are:

 

Wed Sep  6 17:35:01 EDT 2023

LNXVP1262

Wed Sep  6 17:35:02 EDT 2023

Wed Sep  6 17:35:12 EDT 2023

LNXVP1251

Wed Sep  6 17:35:13 EDT 2023

Wed Sep  6 17:35:23 EDT 2023

 

Is the (--sshlogin) login order always alphabetical (I am assuming) or is there a way to force a sort order.  I suppose one hack is creating SSH machine aliases in a sort order, and hope parallel can use the aliases, but that’s ugly.

 

 

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.