re: [Condor-users] SIGNIFICANT_ATTRIBUTES

["Todd Tannenbaum" <tannenba@xxxxxxxxxxx>]

Bruce Beckles <mbb10@xxxxxxxxx> wrote:
__________
>
>Please can someone from the Condor Team please provide some documentation 
>for the "SIGNIFICANT_ATTRIBUTES" setting?  The only thing I can find is a 
>few brief mentions of it on slides in various presentations.
>

hi bruce.

The reason for the lack of documentation on this setting is soon Condor will set it correctly automatically, and thus folks need not worry about it.  :).  This should make it into the developer release within 2 weeks.  Setting it manually is a risky business since modifications of the START expression on execute machines could require a change to the schedd SIGNIFICANT_ATTRIBUTES setting.  By having Condor keep this setting correct automatically, we remove a significant burden for pools that span across administrative domains.

>I'm assuming that the correct format is:
> 	SIGNIFICANT_ATTRIBUTES = <Job ClassAd attribute>,<Job ClassAd attribute> ...
>e.g.
> 	SIGNIFICANT_ATTRIBUTES = Owner,Cmd,Requirements
>

Correct.

>But is the value of those attributes ANDed or what?, i.e. does the above 
>example mean that all jobs with the same owner *and* the same executable 
>*and* the same job requirements will be considered as the same for 
>matching purposes (i.e. if we can't match one, don't bother trying to 
>match any others in this negotiation cycle)?

Also correct.

>
>And does SIGNIFICANT_ATTRIBUTES have to be set for the schedd or the 
>negotiator (or both?) or some other daemon completely?

Just the schedd I believe.

>
>Thanks,
>
>   Bruce
>

Sure thing.

Best regards and I look forward to seeing you in a few weeks at CondorWeek,
Todd


>--
>Bruce Beckles,
>e-Science Specialist,
>University of Cambridge Computing Service.
>_______________________________________________
>Condor-users mailing list
>Condor-users@xxxxxxxxxxx
>https://lists.cs.wisc.edu/mailman/listinfo/condor-users