Re: [Condor-users] auto-clustering of attributes

[Horvátth Szabolcs <szabolcs@xxxxxxxxxxxxx>]

Thanks for the information Todd and Matt!
After taking a closer look at the clustered attributes and the 
AutoClusterId condor did indeed recompute the id properly
after attribute changes. So my execution-order change is not caused by 
auto-clustering (although I still don't know what's
happening, it used to work nicely).

Cheers,
Szabolcs


Matt Hope wrote:
> It is possible the OP was referring to the RANK *after* the job has
> begun running.
>
> This appears *not* to be recomputed if the underlying values driving
> it or the calculation mechanism is changed. At least on 6.6.
>
> This means massive changes to the way RANK is calculated such that
> previous numbers are wholly inappropriate in relation to the old ones
> can cause your farm to suddenly toss all of it's jobs away. (Happened
> to me once - never allow RANK expression changes to be rolled out to
> your pool en-masse. especially if the new numbers are going to be
> inflated).
>
> I do not know if this is a feature of the startd, the negotiator or
> interaction of both (at the time I didn't have the source so just took
> it as a feature and left it at that) but I believe recalculation is
> the better of the options as it has the more 'obvious' behaviour.
>
> So in answer to the OP - at the moment what you appear to want is not
> possible as far as I can tell - I have not exhausted the possibilities
> available from the periodic_* mechanism but I have a workaround (not
> changing it except when the farm needs a reboot :).
>
> Matt