Just an FYI the CONDUIT latency times continue to slowly increase. Unidata is seeing the same slowly increasing lags, so that suggests to me it is an issue with the source. I don't think we're actually getting data that much later, I think the clock has a slow
drift on conduit.ncep.noaa.gov.
We are not experiencing any real problems with this right now, but if the lag grows larger than 3600 seconds, I am concerned we will begin losing data, since (as I understand it) the ldm doesn't ask for data more than an hour old.
Can you please have someone look into this at some point? Thanks,
Pete
From: Dustin Sheffler - NOAA Federal <address@hidden>
Sent: Friday, June 5, 2020 1:50 PM To: Pete Pokrandt <address@hidden> Cc: Carissa Klemmer - NOAA Federal <address@hidden>; Anne Myckow - NOAA Federal <address@hidden>; _NCEP.List.pmb-dataflow <address@hidden> Subject: Re: [Ncep.list.pmb-dataflow] [conduit] NCEP CONDUIT Outage planned Hi Pete,
Thank you for passing along the information about the increasing lag times your seeing for CONDUIT ingest. That is a very interesting and telling graph for a slowly worsening issue. We will investigate and let you know what we find.
-Dustin
On Tue, Jun 2, 2020 at 5:15 PM 'Pete Pokrandt' via _NCEP list.pmb-dataflow <address@hidden> wrote:
|
_______________________________________________ NOTE: All exchanges posted to Unidata maintained email lists are recorded in the Unidata inquiry tracking system and made publicly available through the web. Users who post to any of the lists we maintain are reminded to remove any personal information that they do not want to be made public. conduit mailing list address@hidden For list information or to unsubscribe, visit: https://www.unidata.ucar.edu/mailing_lists/