[LDM #DBK-582040]: 6.10.1 how to diagnose pqact memory leak?

Daryl,

> I think I figured it out, this pqact entry:
> 
> NEXRD2  
> ^L2-([^/]*)/(....)/([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9][0-5][0-9])
> FILE    /mnt/mtarchive/nexrd2/raw/\2/\2_\3_\4
> 
> will leak descriptors to the limit allowed by the OPEN_MAX, which is
> 65768 on my system.  The memory consumption gets a bit out of hand
> with these many fds it appears.  Changing to:
> 
> NEXRD2  
> ^L2-([^/]*)/(....)/([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9][0-5][0-9])
> FILE    -close /mnt/mtarchive/nexrd2/raw/\2/\2_\3_\4
> 
> keeps things in check, probably at some performance penalty.
> 
> Am I on the right track?

That sounds right. Without the "-close" option, the FILE action will keep open 
every output file (in order to append the next matching data-product) until the 
pqact(1) process reaches the limit on the number of open files and begins 
closing the least recently used ones. If there are a lot of different output 
file names, then there will be a lot of open files. Each file will have an 
associated output buffer.

> daryl

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: DBK-582040
Department: Support LDM
Priority: Normal
Status: Closed