[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] collector hierarchy burst
- Date: Wed, 19 Mar 2014 16:57:57 +0100
- From: Pek Daniel <pekdaniel@xxxxxxxxx>
- Subject: Re: [HTCondor-users] collector hierarchy burst
Thanks for the hint!
By the way, as far as I know in case of condor_startd there's an
option for this purpose:
But I suppose currently there's no counterpart of this option for the
2014-03-18 14:43 GMT+01:00 Brian Bockelman <bbockelm@xxxxxxxxxxx>:
> Hi Daniel,
> Probably not (but I didn't look at the code so I'm not sure).
> You can set the update interval for each to include a random element with the special $RANDOM_INTEGER() config macro. See http://research.cs.wisc.edu/htcondor/manual/v8.1/3_3Configuration.html#SECTION00432000000000000000.
> I opened a ticket to investigate this issue: https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4264
> On Mar 14, 2014, at 5:23 AM, Pek Daniel <pekdaniel@xxxxxxxxx> wrote:
>> I've set up a collector hierarchy on two machines with 50 subcollector
>> / machine, and a main collector. My question is that if I start up the
>> collector daemons more-or-less at the same time (DAEMON_LIST =
>> $(DAEMON_LIST) COLLECTOR2 COLLECTOR3 ...), are the subcollectors
>> clever enough not to send their periodic ClassAd updates at the very
>> same time to the main collector causing a burst?
>> HTCondor-users mailing list
>> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> The archives can be found at:
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: