Re: [HTCondor-users] File last modification time or job last write() attribute?

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

On 5/25/2016 1:07 PM, Iain Bradford Steers wrote:
> There’s also a delayed set available via the condor_chirp utility.
>
> Gets back to the schedd with a maximum of 15-minutes delay IIRC.
>
> Cheers, Iain

+1

The chirp command is set_job_attr_delayed.  From the manual ( see 
https://is.gd/PyO8Bh ) :

set_job_attr_delayed JobAttributeName AttributeValue
    Sets the named job ClassAd attribute with the given attribute 
value, but does not immediately synchronize the value with the submit 
side. It can take 15 minutes before the synchronization occurs. This has 
much less overhead than the non delayed version. With this option, jobs 
do not need ClassAd attribute WantIOProxy set. With this option, job 
attribute names are restricted to begin with the case sensitive 
substring Chirp.

regards
Todd

> > On May 25, 2016, at 19:58, Michael V Pelletier
> > <Michael.V.Pelletier@xxxxxxxxxxxx
> > <mailto:Michael.V.Pelletier@xxxxxxxxxxxx>> wrote:
> >
> > From: Iain Bradford Steers <iain.steers@xxxxxxx
> > <mailto:iain.steers@xxxxxxx>>
> > Date: 05/25/2016 01:37 PM
> >
> > > Hi Michael,
> > >
> > > I’m not aware of an existing classad attr that gives that information.
> > >
> > > In theory condor_chirp could be used to update a timestamp of the last
> > > file write to those files.
> > >
> > > Scalability would have me concerned but perhaps you could register an
> > > inotify watcher in the user_job_wrapper and have a condor_chirp call as
> > > part of the inotify callback.
> > >
> > > Cheers, Iain
> >
> > The inotify idea is interesting, though I would definitely see
> > scalability
> > challenges with that approach. Wouldn't want to chirp on every write,
> > that's
> > for sure. The 5-minute interval of the update_job_info hook seems
> > like it would address scalability concerns but still keep enough
> > granularity to make the data useful in expressions. But being able to do
> > it without occupying the HookKeyword would be handy too.
> >
> > Thanks for the suggestion!
> >
> >         -Michael Pelletier.
> > _______________________________________________
> > HTCondor-users mailing list
> > To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx
> > <mailto: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/
>
>
>
> _______________________________________________
> 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/


--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685