We see the same here at NOAA/GSL. Here is our CONDUIT latency trace for the
last 6 months. The drift started in early May. Prior to that, latency was
flat and <10s.
[image: CONDUIT_latency_20201028.png]
Bob Lipschutz
NOAA/ESRL/Global Systems Lab (formerly GSD)
IT Services/Data Services Group
dsg.its.gsl@xxxxxxxx
On Wed, Oct 28, 2020 at 4:55 PM Herzmann, Daryl E [AGRON] <
akrherz@xxxxxxxxxxx> wrote:
> Greetings (emailing the right list this time!),
>
> It has been mentioned a few times on this list that there is a clock drift
> issue with the CONDUIT LDM feed emitting from NCO/IDP. I'd like to ping
> this issue again and see if NCO can please check that system clocks are
> being synced there. The attached plot of feed latency shows the building
> of latency with time from my monitoring, which is a tell tale sign of clock
> drift.
>
> thanks!
> daryl
>
> --
> /**
> * daryl herzmann
> * Systems Analyst III -- Iowa Environmental Mesonet
> * https://mesonet.agron.iastate.edu
> */
> _______________________________________________
> 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
> conduit@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> https://www.unidata.ucar.edu/mailing_lists/
>
