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

[Stefano Dal Pra <stefano.dalpra@xxxxxxxxxxxx>]

Hi Christoph,

condor_status -compact -direct <wn-name> -af START_NOTEBOOK
would report the value as known by that startd at that moment

condor_status -compact <wn-name> -af START_NOTEBOOK
would report the most recent value collected by the central manager for 
that machine.

I think that a match with a candidate job would happen with the value at 
the startd
and a claim would happen with the (sligthly older) value known by the 
negotiator.

One doubt: the script output is not buffered, right? Otherwise you could 
see the output of 6 or more runs ago...
Stefano


On 27/08/21 11:57, Beyer, Christoph wrote:
> 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