Re: [Condor-users] NEGOTIATE_ALL_JOBS_IN_CLUSTER

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

Steffen Grunewald wrote:
> > Starting back w/ Condor v7.0.x and above, the default built-in auto 
> > clustering mechanism in Condor should prevent the situations you 
> > describe above --- and do so in a much more efficient/scalable manner 
> > than setting NEGOTIATE_ALL_JOBS_IN_CLUSTER to TRUE (which is the kiss of 
> > performance death if you have thousands of jobs).
>
> This means I shouldn't touch the default setting then?

Correct, I would keep NEGOTIATE_ALL_JOBS_IN_CLUSTER = False (the 
default) with Condor v7.0.x or above.

The problems you mentioned earlier, such as jobs in a cluster not being 
scheduled if an earlier job in the cluster cannot, should not happen w/ 
v7.0.x as all jobs are considered "independently" by the autoclustering. 
 In other words, jobs are "clustered automatically" now by the schedd 
instead of explicitly by the user - so for negotiation it doesn't matter 
if you submitted them all in one big cluster or not.

> > > Is it possible to - e.g. once per given time period (4 hours?) - "flush"
> > > the queue by temporarily setting the macro to True?
> > Maybe something else is going on?  With Condor v7.0.x and above with the 
> > default auto-clustering, I assert you should never have to resort to 
> > NEGOTIATE_ALL_JOBS_IN_CLUSTER = True.    Are you over-riding 
> > autoclustering in your config file by expliciting setting 
> > SIGNIFICANT_ATTRIBUTES or some such on your condor_config on your submit 
> > hosts?
>
> No, and I never considered to.

Excellent.  :).


--
Todd Tannenbaum                       University of Wisconsin-Madison
Condor Project Research               Department of Computer Sciences
tannenba@xxxxxxxxxxx                  1210 W. Dayton St. Rm #4257