On 08/23/2016 10:32 AM, Ben Cotton wrote:
is there a way to configure HTCondor so that it sends a new job to an idle node that has been idle for most of the time, instead of sending it to another currently idle node which is used by its owner 90% of the time (and therefore has a very high probability to suspend the job after a short time)?
I don't know what the usage patterns of your machines are, but I bet that steering jobs to machines that have highest KeyboardIdle will work out well, statistically speaking.
-greg