[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #DRV-310603]: -close switch



Erik,

My colleague, Tom Yoksas, pointed-out a situation that might be relevant
if you're running the LDM in a container or your system allows a process to
have a huge number of open file descriptors.

BEGIN QUOTE

What we see is that the number of file descriptors in the container is
HUGE, so not adding a '-close' option to FILE actions will result in
disk space "disappearing' even though data scouring is running.  The
problem is that 'scour' is trying to remove files that are not closed,
and the disk space that the files use is not being returned back to
the system, and eventually (like after a couple/three days), the file
system fills.  A restart of the LDM in the container causes all file
open files to be closed, and the "missing" disk space magically
reappears.  We never run into this situation on our motherlode-class
machines since we are keeping lots of days of data, so open files are
being closed in order to free up descriptors.  Julien has tried setting
the number of file descriptors in the container, and that seems to work
most, but not all, of the time.

END QUOTE

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: DRV-310603
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.



NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.