[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Preferring execute nodes that are seldomly used by the owner


There's the TotalTimeOwnerIdle attribute (see
     The number of seconds that this machine (slot) has accumulated
within the owner idle state and activity pair since the condor_startd
began executing. This attribute will only be defined if it has a value
greater than 0.

So you could set a rank expression to prefer (1/TotalTimeOwnerIdle).
If you want to make it percentage-based instead of a count of seconds,
I'd define an attribute on your execute machines like:
    OwnerFactor = (CurrentTime - DaemonStartTime) / TotalTimeOwnerIdle

and then just rank based on OwnerFactor. With either of the above
suggestions, you might want to use an ifThenElse to prevent ending up
with an undefined value.

If you want to get _really_ fancy and collect data across daemon
starts, you can write a startd cron to write the slot state to a
round-robin database and return the percentage of time in owner state
as a classad attribute. That's probably not going to give you a very
good return on your effort unless your daemons restart a lot.

On Tue, Aug 23, 2016 at 9:37 AM, Friedhelm Assendorf
<friedhelm.assendorf@xxxxxxxxxxxx> wrote:
> Hi,
> 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)?
> Cheers,
> Friedhelm
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

Ben Cotton
Technical Marketing Manager

Cycle Computing
Better Answers. Faster.

twitter: @cyclecomputing