Re: [Condor-users] Update_intervals for Negotiator

[Johnson koil Raj <johnson.raj@xxxxxxxxx>]

Hi Rob,
 
we face the following issue and changes what we made in config files 

Error: Could not connect to negotiator ((null)). So the Job is in Idle
State for long time till the Negotiator is available.

#condor_status -negotiator 
       gives nothing at that particular time.

(you can see the Negotiator log files at various instance at this mail
https://lists.cs.wisc.edu/archive/condor-users/2008-October/msg00091.shtml )

we made following changes in config files for our work.

CLASSAD_LIFETIME = 120 
NEGOTIATOR_INTERVAL  = 60

UPDATE_INTERVAL = 60 for startd to update ClassAds frequently to collector


we noticed that Negotiator is Updating collector once in 300 min, though classad_lifetime is 120 the collector is deleting Negotiator classAds, so we are getting nothing  when we give condor_status -negotiator.

so we changed classad_lifetime = 360 now the problem is not frequently occurs, but we have that.

so I need an update_interval parameter to force the Negotiator to send classAds frequently like startd to collector.

why negotiator is behaving like this 

Thanks for reply

by
Johnson


On Thu, 2009-01-29 at 16:43 -0600, Robert Rati wrote:
> Looking at your question agin, you might want NEGOTIATOR_UPDATE_INTERVAL 
> instead.  Could you clarify what you are wanting to do?  Specifically, 
> what you mean by "like what we are doing in the startd".
>
> Rob
>
> Johnson koil Raj wrote:
> > Hi,
> > 
> >     Is there is any configuration parameter that will help to change 
> > Negotiator update intervals to collector like what we are doing in Startd.
> > 
> > by
> > Johnson
> > 
> > * Please do not print this email unless it is absolutely necessary. *
> > 
> > The information contained in this electronic message and any attachments 
> > to this message are intended for the exclusive use of the addressee(s) 
> > and may contain proprietary, confidential or privileged information. If 
> > you are not the intended recipient, you should not disseminate, 
> > distribute or copy this e-mail. Please notify the sender immediately and 
> > destroy all copies of this message and any attachments.
> > 
> > WARNING: Computer viruses can be transmitted via email. The recipient 
> > should check this email and any attachments for the presence of viruses. 
> > The company accepts no liability for any damage caused by any virus 
> > transmitted by this email.
> > 
> > www.wipro.com
> > 
> > 
> > ------------------------------------------------------------------------
> > 
> > _______________________________________________
> > 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: 
> > https://lists.cs.wisc.edu/archive/condor-users/
> _______________________________________________
> 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: 
> https://lists.cs.wisc.edu/archive/condor-users/

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com