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

[IDD #AIZ-345619]: LDM: pattern in ldmd.conf and pact.conf no longer works for CONDUIT??

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: [IDD #AIZ-345619]: LDM: pattern in ldmd.conf and pact.conf no longer works for CONDUIT??
  • Date: Mon, 20 Jul 2020 09:02:32 -0600
Hi Christian,

> What would be the recommended size for the LDM queue size?

That depends on the rate that you receive data. We recommend a queue large 
enough so that the age of the oldest product in the queue is greater than one 
hour. To determine this size, one can either add up the rates of the various 
feeds (which is difficult in your case because you get a subset of the CONDUIT 
feed) or use the "ldmadmin addmetrics" and "ldmadmin plotmetrics" commands to 
see a time-series of the age of the oldest product (that's my preferred 
method). If the minimum age is, say, 30 minutes, then the queue size would need 
to be doubled.

Information on the "metrics" commands can be found at 
<https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/monitoring.html#metrics>.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: AIZ-345619
Department: Support IDD
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.