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

[LDM #UOJ-259840]: Late data not getting past relay

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 #UOJ-259840]: Late data not getting past relay
  • Date: Fri, 06 Oct 2006 12:37:36 -0600
Art,

> Good question.  I'm not sure I know the answer.  Why would the downstream
> LDM's start getting the data starting with timestamps that match the
> restart times of the downstream LDM's for CONDUIT, but not the other
> streams?  Do we know if the upstream node is not sending the data or if
> the downstream node is rejecting it?  Somehow, one of the systems is
> taking the restart time of the downstream LDM and using that to decide
> whether to either send the data or receive it.  Could this be caused by
> queue corruption?

It sounds like the value of the "-o" option on the downstream LDM-s was small 
(e.g., 60) -- so they would accept relatively old CONDUIT data-products (the 
"-m" option), but not request them.  Look in the LDM log file on "idd-ingest" 
for the connections from the downstream LDM-s.  The message will specify the 
start-time for the CONDUIT data.  This information should also be in the 
downstream LDM log files.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UOJ-259840
Department: Support LDM
Priority: Normal
Status: Closed