Re: [HTCondor-users] 2 to 3 minute gap between run of startd_cron and update of classadd ?

[John M Knoeller <johnkn@xxxxxxxxxxx>]

That 3 minutes is how long it takes for the STARTD to decide it needs to update the collector.   You can force a collector update right away by saying so in the output of your STARTD cron script. 

just put

 - update:true

As the last line of output when you want a Collector update right away.  But maybe do this only when the state of the flag changes? 

Hooks — HTCondor Manual 9.1.3 documentation

But even if the collector has not yet been updated, when the STARTD evaluates policy expressions, it will always use the latest result from your startd cron script.  

-tj

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Beyer, Christoph <christoph.beyer@xxxxxxx>
Sent: Friday, August 27, 2021 4:57 AM
To: htcondor-users <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] 2 to 3 minute gap between run of startd_cron and update of classadd ?

 

Hi,

I am using startd_cron to run a script every 30s that returns a classadd called

START_NOTEBOOK = true/false

Everything looks ok, but once the return from the script changes from true to false it takes the startd roughly 3 minutes (thats 5 to 6 more cron runs) to reflect the change in classadd value.

Is this 'to-be-expected' or is there a way to make this mor speedy or is it me being stupid (possible, happened before) ;)

Best
christoph

--
Christoph Beyer
DESY Hamburg
IT-Department

Notkestr. 85
Building 02b, Room 009
22607 Hamburg

phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/