| Mailing List ArchivesAuthenticated access |  | ![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif)  | 
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Match-making delays/errors in Condor-G
- Date: Fri, 25 Apr 2008 17:17:23 +0200
- From: Jan Ploski <Jan.Ploski@xxxxxxxx>
- Subject: Re: [Condor-users] Match-making delays/errors in Condor-G
condor-users-bounces@xxxxxxxxxxx schrieb am 04/25/2008 04:41:14 PM:
> condor-users-bounces@xxxxxxxxxxx schrieb am 04/25/2008 04:06:47 PM:
> 
> > 
> > Todd may be able to correct me or explain why, but my guess is that 
you 
> > can work around this problem with the following configuration setting 
> > for the negotiator:
> > 
> > NEGOTIATOR_MATCHLIST_CACHING = False
> 
> Thanks for the tip! This (undocumented?) option indeed eliminates the 
> problem.
Maybe I was happy too soon: another problem seems to have been introduced 
now. Even though the first 100 jobs or so got submitted, the remaining 20 
now just remain Idle (JobStatus == 1 according to condor_q) and 
unsubmitted. NegotiatorLog repeatedly contains
4/25 17:12:46 Phase 4.1:  Negotiating with schedds ...
4/25 17:12:46     NumStartdAds = 3
4/25 17:12:46     NormalFactor = 1.000000
4/25 17:12:46     MaxPrioValue = 4.000000
4/25 17:12:46     NumScheddAds = 1
4/25 17:12:46   Negotiating with jploski@xxxxxxxxxxxxxxxxxxxxxx skipped 
because no idle jobs
4/25 17:12:46   Schedd jploski@xxxxxxxxxxxxxxxxxxxxxx got all it wants; 
removing it.
What can I do to diagnose it?
Regards,
Jan Ploski