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

[LDM #VAP-368514]: Primary/alternate switching mixes in old data with new

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: [LDM #VAP-368514]: Primary/alternate switching mixes in old data with new
  • Date: Mon, 23 Nov 2009 14:02:30 -0700
Art,

> I define $max_latency=21600 in ldmadmin-pl.conf.

That's a long time.  The product-queue on idd.cise-nsf.gov certainly isn't that 
big.

What's the minimum residency-time in your product-queue?  The LDM package 
should be configured to always request data that is more recent than the oldest 
data-product in the queue.

> >    fgrep '[<pid>]' $HOME/logs/ldmd.log | fgrep 'LDM-6 desired product-class'
> 
> Nov 23 05:47:56 iddrs3 idd.cise-nsf.gov[3392] NOTE: LDM-6 desired
> product-class: 20091122234756.631 TS_ENDT {{CONDUIT,  ".*"},{NONE,
> "SIG=5ac6517b97857d9a8205a1a39d98e5d3"}}
...

Thanks.  That's what I expected.


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VAP-368514
Department: Support LDM
Priority: Normal
Status: Closed