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

[TIGGE #YZT-357848]: queue size and pqmon

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [TIGGE #YZT-357848]: queue size and pqmon
  • Date: Thu, 02 Nov 2006 11:48:49 -0700
Manuel,

> Bingo!
> 
> There was a pqcat running from 2nd October:
> ldm@tigge-ldm:~/data>  ps -elf | grep pqcat
> 0 S ldm      11318  8011  0  76   0 - 1004484 write_ Oct02 pts/1
> 00:00:00 pqcat -O -v
> 0 S ldm       4901   655  0  76   0 -   956 pipe_w 18:39 pts/2
> 00:00:00 grep pqcat

Excellent!

> After I killed it, pqmon shows more reasonable output:
> ldm@tigge-ldm:~> pqmon
> Nov 02 18:40:03 pqmon NOTE: Starting Up (5132)
> Nov 02 18:40:03 pqmon NOTE: nprods nfree  nempty      nbytes  maxprods
> maxfree  minempty    maxext  age
> Nov 02 18:40:03 pqmon NOTE:   7377    20  969165  3998346032     82186
> 5094    894302    411776 1152
> Nov 02 18:40:03 pqmon NOTE: Exiting

1152 seconds is a more reasonable age for the oldest product
in the queue.  It is a bit small, however.  If a downstream
LDM that has a new product-queue connects, then it will ask
for data for the past hour -- data that won't be in your
queue.  Also, if a downstream site has to go offline to fix
a problem, then they only have 1152 seconds to fix the problem.

Good luck.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YZT-357848
Department: Support IDD TIGGE
Priority: Normal
Status: Closed