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

[LDM #WSP-283484]: latency between receiving and writing NNEXRAD


> I've got a problem on dc-ldm2.tamu.edu in that we're seeing a delay of
> some 3-4 hours in writing NNEXRAD data to disk.  Of course, this makes
> creating current radar products problemmatical.
> We've also been seeing some latency in writing CONDUIT-derived GFS 0.5
> deg data which suggests this system might have a problem.
> Any thoughts on what I should check?

Where are you getting the NNEXRAD data?  If from an upstream LDM, then
what does a "notifyme -vl- -f NNEXRAD -h <<remote host>>" show when
compared to a "notifyme -vl- -f NNEXRAD"?

> A quick pqmon shows:
> address@hidden N0R]$ pqmon
> Oct 22 15:22:08 pqmon NOTE: Starting Up (4590)
> Oct 22 15:22:08 pqmon NOTE: nprods nfree  nempty      nbytes  maxprods
> maxfree  minempty    maxext  age
> Oct 22 15:22:08 pqmon NOTE: 662219    10 2267458 11732671688    688081
> 171   2241605  39103184 18610
> Oct 22 15:22:08 pqmon NOTE: Exiting
> --
> Gerry Creager -- address@hidden
> Texas Mesonet -- AATLT, Texas A&M University
> Cell: 979.229.5301 Office: 979.862.3982 FAX: 979.862.3983
> Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843

Steve Emmerson

Ticket Details
Ticket ID: WSP-283484
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.