We have recently implemented a caching scheme that ends up storing job input
files in GLOBUS_SCRATCH_DIR (and these files are not subsequently cleaned up
when the job finishes, hence the term "cache" =)  This is all working well,
but the part that has not been implemented yet is some kind of cache
eviction scheme.  Leaving the criteria for when files should be removed from
the cache aside for the moment, my question is this: is there a way using
existing Globus mechanisms to monitor the size of GLOBUS_SCRATCH_DIR (or to
put it another way, the amount of free space on the partition containing the
scratch directory?)  And, if the partition is close to filling up, is there
a way to delete those files?  Just looking for ideas & suggestions right
now, thanks!

Adam

Reply via email to