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

[Support #NKX-533675]: Performances issues with large ldm queues

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: [Support #NKX-533675]: Performances issues with large ldm queues
  • Date: Tue, 23 Jan 2007 09:54:41 -0700
Baudouin,

> Does that mean that all ldm must be upgraded at the same time?

Not because of the LDM, itself.  In the LDM system, the MD5 signature is 
computed only once, when the data-product is created.  Thereafter, the 
signature is only used by the LDM system to determine if the data-product is 
already in the product-queue.  Consequently, changing the procedure by which 
it's created only affect the system that's creating the data-product.

If, however, the MD5 signature is used by processes outside the LDM -- such as 
an ancillary process that verifies reception of data-products -- then, yes, 
that and similar processes would have to know about the new procedure for 
computing the MD5 signature.


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NKX-533675
Department: Support IDD TIGGE
Priority: Normal
Status: On Hold