Re: [Condor-users] autoclusterattrs (fwd)

[Steven Timm <timm@xxxxxxxx>]

> Steve -
>
> I don't think autoclusters are the problem.  We've recently discovered an issue with Condor-G matching only once per resource ad is an issue with the matchlist caching (which is yet another mechanism that speeds up the matchmaking process in the "regular" case).  It is on our list to fix this with Condor-G matching.  Discovery of this bug is credited to our friends in Italy at INFN working on egee (thanks Francesco!).  For now, you can workaround the problem by putting the following into your negotiator's condor_config :
>   NEGOTIATOR_MATCHLIST_CACHING = False
>  (normally it defaults to true)
> Then restart the negotiator.  Hopefully this will restore the ability to match a given resource multiple times per cycle (assuming you've set things up this way) until we get around to fixing the issue in the caching code.
>
> hope this helps
> Todd

I have made the change to turn off NEGOTIATOR_MATCHLIST_CACHING.
and the match rate has gone up.
But I asked the larger question about autoclustering because
I observed two condor pools, one in which the autoclusterattr
of all the outbound grid jobs were the same, and
one where all the outbound grid jobs had no autoclusterattr
field at all.

They were both running condor 6.8.3 andd I didn't make
any changes to autoclusterattrs on either machines.

Steve


> ---
> Todd Tannenbaum
> Dept of Computer Sciences
> University of Wisconsin-Madison
> <-- Sent from a Palm Treo 680 -->
>
> -----Original Message-----
>
> From:  Steven Timm <timm@xxxxxxxx>
> Subj:  [Condor-users] autoclusterattrs (fwd)
> Date:  Mon Mar 5, 2007 6:54 pm
> Size:  1K
> To:  condor-users@xxxxxxxxxxx
>
>
>
> ------------------------------------------------------------------
> Steven C. Timm, Ph.D  (630) 840-8525
> timm@xxxxxxxx  http://home.fnal.gov/~timm/
> Fermilab Computing Division, Scientific Computing Facilities,
> Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.
>
> ---------- Forwarded message ----------
> Date: Mon, 5 Mar 2007 18:39:02 -0600 (CST)
> From: Steven Timm <timm@xxxxxxxx>
> To: condor_users@xxxxxxxxxxx
> Subject: autoclusterattrs
>
>
> How do you change the AutoClusterAttrs
> I am in a situation where I am using Condor-G matchmaking
> but somehow all the AutoClusterAttrs of all the jobs in the
> queue are the same, and thus only one job per negotiation cycle
> can get matched to any remote resource.
> I know it is possible to set the attribute NEGOTIATE_ALL_JOBS_IN_CLUSTER
> to get around this.. but I am wondering in general how do we
> set the AutoClusterAttrs.. I thought this use to be in
> the condor manual but I can't find autoclusterattrs anywhere in
> the manual now.
>
> Steve
>
>
> ------------------------------------------------------------------
> Steven C. Timm, Ph.D  (630) 840-8525
> timm@xxxxxxxx  http://home.fnal.gov/~timm/
> Fermilab Computing Division, Scientific Computing Facilities,
> Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR