Re: [HTCondor-users] Current ClassAd values in job files [.job.ad, .machine.ad] ?

[Brian Bockelman <bbockelm@xxxxxxxxxxx>]

Hi,

Itâs important to note that you only need WantIOProxy to do âimmediateâ updates.

Immediate updates can have scalability issues because they are new interaction between the worker node and the schedd.  However, they are sometimes necessary if something needs to know ASAP a job progress update (maybe to kick off another job?).  Two back-to-back attribute updates will incur twice the load at the schedd.

On the other hand, you can use âcondor_chirp set_job_attr_delayedâ for delayed updates - they are pushed to the schedd along with the regularly scheduled resource usage updates.  I find this better - and much more scalable - for monitoring.  Multiple updates are batched into a single schedd update.

Hope this helps,

Brian

> On Apr 13, 2016, at 9:26 AM, Iain Bradford Steers <iain.steers@xxxxxxx> wrote:
> 
> Hi Thomas,
> 
> If you want to edit/add the attributes in the job classad then you should set wantIOProxy = True in the job submission and use condor_chirp to update the values in the job classad.
> 
> This update will get passed back to the schedd via the shadow.
> 
> Not sure what would happen if you tried to manually change the machine.ad.
> 
> Cheers, Iain
> ________________________________________
> From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of Thomas Hartmann [thomas.hartmann@xxxxxxx]
> Sent: 13 April 2016 16:20
> To: HTCondor-Users Mail List
> Subject: [HTCondor-users] Current ClassAd values in job files [.job.ad, .machine.ad] ?
> 
> Hi all,
> 
> I stumbled over the job's ClassAd files
> /var/lib/condor/execute/dir_PID/{.job.ad,.machine.ad}
> 
> Represent the files/ClassAds the current values of a jobs or do they
> contain the values at start (with the current values in memory not
> flushed to disk)? (*)
> 
> Cheers and thanks,
>  Thomas
> 
> (*) what would happen, if one would try to manipulated the files' values
> or try to add keys...?
> 
> _______________________________________________
> 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/