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

Re: Fwd: Re: [conduit] Slow connection/big lag from conduit.ncep.noaa.gov

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: Re: Fwd: Re: [conduit] Slow connection/big lag from conduit.ncep.noaa.gov
  • Date: Thu, 02 Apr 2015 15:50:12 -0500
I was alerted to it on Sunday evening (March 29) and apparently it had been happening for a few days already.
Oddly enough, I have switched back over to feeding from conduit.ncep.noaa.gov and my latencies are back down under 60 seconds or so. I thought you did something, restarted the ldm on conduit.ncep.noaa.gov or something, but it appears whatever was going on has been resolved. 

I'll let you know if it happens again.

Pete


On 04/02/2015 03:43 PM, address@hidden wrote:

Pete,

Thanks for the information, I am still looking into this, have not yet found 
the root cause of the latency increase. You said it started on Monday or before 
that?

---
Kyle Nevins
NCWCP_HELPDESK

On Wed, 01 Apr 2015 16:28:22 -0400, Pete Pokrandt <address@hidden> wrote:

Kyle,

I had changed to feed conduit from idd.unidata.ucar.edu for a while, as
a result of the slow connection to conduit.ncep.noaa.gov. Just earlier
this afternoon I changed back. I currently have this in my ldmd.conf on
idd.aos.wisc.edu:

REQUEST CONDUIT "[05]$" ncepldm4.woc.noaa.gov
REQUEST CONDUIT "[16]$" ncepldm4.woc.noaa.gov
REQUEST CONDUIT "[27]$" ncepldm4.woc.noaa.gov
REQUEST CONDUIT "[38]$" ncepldm4.woc.noaa.gov
REQUEST CONDUIT "[49]$" ncepldm4.woc.noaa.gov
REQUEST CONDUIT "[05]$" conduit.ncep.noaa.gov
REQUEST CONDUIT "[16]$" conduit.ncep.noaa.gov
REQUEST CONDUIT "[27]$" conduit.ncep.noaa.gov
REQUEST CONDUIT "[38]$" conduit.ncep.noaa.gov
REQUEST CONDUIT "[49]$" conduit.ncep.noaa.gov

Pete



On 04/01/2015 03:24 PM, address@hidden wrote:

Hi Pete,

So it looks like you are only going to one of our conduit servers and I'm 
trying to determine if that is our load balancer or not. Can you confirm that 
your LDM feed goes to conduit.ncep.noaa.gov (140.90.101.42)? Thanks.

---
Kyle Nevins
NCWCP_HELPDESK

On Tue, 31 Mar 2015 12:05:18 -0400, Pete Pokrandt <address@hidden> wrote:

Per the below response, I am submitting a ticket to the NCWCP Help
desk.  See my description of the slow connection between
conduit.ncep.noaa.gov and idd.aos.wisc.edu below.

Thanks,
Pete



-------- Forwarded Message --------
Subject:        Re: [conduit] Slow connection/big lag from conduit.ncep.noaa.gov
Date:   Tue, 31 Mar 2015 10:56:11 -0400
From:   Justin Cooke - NOAA Federal <address@hidden>
To:     Pete Pokrandt <address@hidden>, NCWCP helpdesk - NOAA Service
Account <address@hidden>
CC:     address@hidden <address@hidden>



Pete,

Please submit a ticket to the NCWCP Helpdesk (address@hidden
<mailto:address@hidden>), someone on our system administration
team will look into why you're seeing degraded performance from
conduit.ncep.noaa.gov <http://conduit.ncep.noaa.gov>

Justin Cooke
NCEP Central Operations

On Tue, Mar 31, 2015 at 10:45 AM, Pete Pokrandt <address@hidden
<mailto:address@hidden>> wrote:

      The past few days my connection for conduit data feeding from
      conduit.ncep.noaa.gov <http://conduit.ncep.noaa.gov> (to
      idd.aos.wisc.edu <http://idd.aos.wisc.edu>) has become slower,
      resulting in large lag times and lost data.

      The attached gif shows my lag over the past few days. There are no
      time stamps on the image, unfortunately, but the large peaks are
      from each 6 hrly GFS/ensemble suite. The right side of the graph is
      now (14:30 UTC Tuesday, March 31) and the left side is ~00 UTC March 29.

      During the open peaks on the left side of the graph, I was feeding
      from conduit.ncep.noaa.gov <http://conduit.ncep.noaa.gov> and
      ncepldm4.woc.noaa.gov <http://ncepldm4.woc.noaa.gov>.

      About half-way across the graph, where the peaks begin to be filled
      in and the green line starts, I added idd.unidata.ucar.edu
      <http://idd.unidata.ucar.edu> to the mix. Lags were still large.

      Prior to the 00 UTC run last night (the first of the two lower blue
      peaks on the right hand side) I removed conduit.ncep.noaa.gov
      <http://conduit.ncep.noaa.gov> form my requests, so I am only
      requesting from idd.unidata.ucar.edu <http://idd.unidata.ucar.edu>
      and ncepldm4.woc.noaa.gov <http://ncepldm4.woc.noaa.gov>.

      My perception from this sequence of events is that my connectivity
      to conduit.ncep.noaa.gov <http://conduit.ncep.noaa.gov> has
      degraded. This seems to have begun within the last week or so, I
      didn't have the large lags before.

      Any ideas?

      What are the root conduit servers that I should be feeding from? I
      currently have

      conduit.ncep.noaa.gov <http://conduit.ncep.noaa.gov>
      and
      ncepldm4.woc.noaa.gov <http://ncepldm4.woc.noaa.gov>

      Thanks,
      Pete




      --
      Pete Pokrandt - Systems Programmer
      UW-Madison Dept of Atmospheric and Oceanic Sciences
      608-262-3086 <tel:608-262-3086> - address@hidden
      <mailto:address@hidden>


      _______________________________________________
      conduit mailing list
      address@hidden <mailto:address@hidden>
      For list information or to unsubscribe, visit:
      http://www.unidata.ucar.edu/mailing_lists/



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


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



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