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

Re: [conduit] High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov

Sounds good, thanks!

Pete


-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - address@hidden


From: Anne Myckow - NOAA Federal <address@hidden>
Sent: Friday, August 20, 2021 12:14 PM
To: Pete Pokrandt <address@hidden>
Cc: address@hidden <address@hidden>; address@hidden <address@hidden>; address@hidden <address@hidden>; address@hidden <address@hidden>
Subject: Re: High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
 
Pete,

conduit.ncep.noaa.gov is a load-balanced DNS that points to both conduit1 and conduit2 servers on the backend. I'm going to see if we can push you all off of conduit2 for now, hopefully those of you connected to conduit2 will see a brief interruption and then connect to conduit1 automatically.

More to come.
Anne

On Fri, Aug 20, 2021 at 1:12 PM Pete Pokrandt <address@hidden> wrote:
It looks like conduit.ncep.noaa.gov is pulling data from both vm-lnx-conduit1 and vm-linux-conduit2 - conduit1 seems ok, it's just conduit2 that is showing the large lags.

I don't know how things are set up exactly, but it might work to have conduit.ncep.noaa.gov only request CONDUIT data from vm-lnx-conduit1 until the problem with feeding from conduit2 is resolved? 

Unidata folks, any suggestions from your end?

Thanks, we do appreciate all your work on our behalf!
Pete


-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - address@hidden


From: Anne Myckow - NOAA Federal <address@hidden>
Sent: Friday, August 20, 2021 12:07 PM
To: Pete Pokrandt <address@hidden>
Cc: address@hidden <address@hidden>; address@hidden <address@hidden>; address@hidden <address@hidden>; address@hidden <address@hidden>
Subject: Re: High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
 
Hi Pete,

We have a lot of systems and applications running out of College Park right now, which I think is part of it. But I will have someone take a look at conduit2 today, see if maybe we need to try and move your connections to conduit1 instead.

Thanks,
Anne

On Fri, Aug 20, 2021 at 12:54 PM Pete Pokrandt <address@hidden> wrote:
Dear Anne, Dustin and all,

Did you see this? We are still experiencing high latencies of 800-1000 seconds on our CONDUIT feeds during the times when the GFS comes through that appear to be coming from the host


Here are the most recent lags. Any ideas?

Thanks,
Pete








-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - address@hidden


From: Pete Pokrandt
Sent: Wednesday, August 18, 2021 3:02 PM
To: address@hidden <address@hidden>; address@hidden <address@hidden>; address@hidden <address@hidden>
Cc: address@hidden <address@hidden>; address@hidden <address@hidden>
Subject: High CONDUIT latencies from vm-lnx-conduit2.ncep.noaa.gov
 
Dear Anne, Dustin and all,

Recently we have noticed fairly high latencies on the CONDUIT ldm data feed originating from the machine vm-lnx-conduit2.ncep.noaa.gov. The feed originating from vm-lnx-conduit1.ncep.noaa.gov does not have the high latencies. Unidata and other top level feeds are seeing similar high latencies from vm-lnx-conduit2.ncep.noaa.gov.

Here are some graphs showing the latencies that I'm seeing:

From https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd-agg.aos.wisc.edu - latencies for CONDUIT data arriving at our UW-Madison AOS ingest machine






At least here at UW-Madison, these latencies are causing us to lose some data during the large GFS/GEFS periods.

Any idea what might be causing this?

Pete




-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - address@hidden



--
Anne Myckow
Dataflow Team Lead
NWS/NCEP/NCO


--
Anne Myckow
Dataflow Team Lead
NWS/NCEP/NCO
_______________________________________________
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/