[HTCondor-users] HTCondor flock and Negotiator interval

[Vikrant Aggarwal <ervikrant06@xxxxxxxxx>]

Hello Experts,

I want to confirm my understanding about the behavior of requirements and flock_to list:

D is the primary cluster of submitter node which shows up in "condor_host". B, C and A are the pools to which submitter node can flock.

FLOCK_TO = B, C, A

Requirements = ( (MachineOwner=="A") Â|| Â(MachineOwner=="B") Â|| Â(MachineOwner=="C") Â|| (MachineOwner=="D")

My understanding:

- Irrespective of the order it always tries first to find slot in primarly pool in this case D.
- If slot is not available in D then it will start searching for other clusters according to flock order instead of requirement order. So first pool it will look for is B then C (if slots not available in B) and finally A (slots not available in B and C).Â
- If any pool mentioned in flock_to list but not in requirement that will not be considered.

Question:

If my above understanding is correct then how can I force the submit box to try running the job on pool D for 30 mins and if the slots are not available after 30mins then move to the other pools mentioned in requirements.

I believe NEGOTIATOR_ interval settings may help but not sure which one should I tune. All settings are with MAX none with MIN.

Version I am using is 8.5.8

Thanks & Regards,

Vikrant Aggarwal