[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 11:11:50 -0600
Art,

> Yes... -m 28800 for the idd-ingest machine and -m 21600 for the two
> machines feeding from idd-ingest.  The downstream machines were getting
> data from the idd-ingest machine, but not CONDUIT although the CONDUIT
> data was only 2-3 hours old.  Furthermore, I observed that the CONDUIT
> data started to be received by the downstream nodes at the same instant
> that I had most recently restarted them (i.e. an ldmadmin stop/start).
> In other words, the time stamp of the first CONDUIT data to start coming
> in on the downstream node matched the most recent ldmadmin stop/start time
> of that node.  This occurred, of course, when the idd-ingest machine had
> caught up on CONDUIT data to that point in time as well.  As I mentioned
> above, I'm pretty sure this type of problem has occurred before, but the
> current case seemed pretty clear to me which is why I bring it up.
> 
> Any ideas?

Could my answer to your other trouble-ticket also explain this?

Regards,
Steve Emmerson

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