NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [conduit] Large lags on CONDUIT feed - started a week or so ago

Art,

I don't know if NCEP ever figured anything out, but I've been able to keep my 
latencies reasonable (300-600s max, mostly during the 12 UTC model suite) by 
splitting my CONDUIT request 10 ways, instead of the 5 that I had been doing, 
or in a single request. Maybe give that a try and see if it helps at all.

Pete



<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx

________________________________
From: Person, Arthur A. <aap1@xxxxxxx>
Sent: Monday, March 11, 2019 3:45 PM
To: Holly Uhlenhake - NOAA Federal; Pete Pokrandt
Cc: conduit@xxxxxxxxxxxxxxxx; support-conduit@xxxxxxxxxxxxxxxx
Subject: Re: [conduit] Large lags on CONDUIT feed - started a week or so ago


Holly,


Was there any resolution to this on the NCEP end?  I'm still seeing terrible 
delays (1000-4000 seconds) receiving data from conduit.ncep.noaa.gov.  It would 
be helpful to know if things are resolved at NCEP's end so I know whether to 
look further down the line.


Thanks...           Art


Arthur A. Person
Assistant Research Professor, System Administrator
Penn State Department of Meteorology and Atmospheric Science
email:  aap1@xxxxxxx, phone:  814-863-1563<callto:814-863-1563>


________________________________
From: conduit-bounces@xxxxxxxxxxxxxxxx <conduit-bounces@xxxxxxxxxxxxxxxx> on 
behalf of Holly Uhlenhake - NOAA Federal <holly.uhlenhake@xxxxxxxx>
Sent: Thursday, February 21, 2019 12:05 PM
To: Pete Pokrandt
Cc: conduit@xxxxxxxxxxxxxxxx; support-conduit@xxxxxxxxxxxxxxxx
Subject: Re: [conduit] Large lags on CONDUIT feed - started a week or so ago

Hi Pete,

We'll take a look and see if we can figure out what might be going on.  We 
haven't done anything to try and address this yet, but based on your analysis 
I'm suspicious that it might be tied to a resource constraint on the VM or the 
blade it resides on.

Thanks,
Holly Uhlenhake
Acting Dataflow Team Lead

On Thu, Feb 21, 2019 at 11:32 AM Pete Pokrandt 
<poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>> wrote:
Just FYI, data is flowing, but the large lags continue.

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.aos.wisc.edu<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frtstats.unidata.ucar.edu%2Fcgi-bin%2Frtstats%2Fiddstats_nc%3FCONDUIT%2Bidd.aos.wisc.edu&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570122684&sdata=5ReQN0dB3%2FfIL9ocMVQGSgs7Rv9lZHfvxr6IzsKfC2c%3D&reserved=0>
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+conduit.unidata.ucar.edu<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frtstats.unidata.ucar.edu%2Fcgi-bin%2Frtstats%2Fiddstats_nc%3FCONDUIT%2Bconduit.unidata.ucar.edu&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570132693&sdata=ME2oBisBGioEn1wPndx8uI66iqiUgH2gO9nMub3iWBY%3D&reserved=0>

Pete



<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.weather.com%2Ftv%2Fshows%2Fwx-geeks%2Fvideo%2Fthe-incredible-shrinking-cold-pool&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570132693&sdata=8WV5O%2F4jNB0cllWeEI6Ze06X1X4bv4IygCnadTcxyxQ%3D&reserved=0>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>

________________________________
From: conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx> 
<conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx>> on 
behalf of Pete Pokrandt <poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>>
Sent: Wednesday, February 20, 2019 12:07 PM
To: Carissa Klemmer - NOAA Federal
Cc: conduit@xxxxxxxxxxxxxxxx<mailto:conduit@xxxxxxxxxxxxxxxx>; 
support-conduit@xxxxxxxxxxxxxxxx<mailto:support-conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] Large lags on CONDUIT feed - started a week or so ago

Data is flowing again - picked up somewhere in the GEFS. Maybe CONDUIT server 
was restarted, or ldm on it? Lags are large (3000s+) but dropping slowly

Pete



<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.weather.com%2Ftv%2Fshows%2Fwx-geeks%2Fvideo%2Fthe-incredible-shrinking-cold-pool&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570142698&sdata=y3refCa5zQubcuoGwMIaqPHUmKZrip0WirYwUsLQHj8%3D&reserved=0>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>

________________________________
From: conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx> 
<conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx>> on 
behalf of Pete Pokrandt <poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>>
Sent: Wednesday, February 20, 2019 11:56 AM
To: Carissa Klemmer - NOAA Federal
Cc: conduit@xxxxxxxxxxxxxxxx<mailto:conduit@xxxxxxxxxxxxxxxx>; 
support-conduit@xxxxxxxxxxxxxxxx<mailto:support-conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] Large lags on CONDUIT feed - started a week or so ago

Just a quick follow-up - we started falling far enough behind (3600+ sec) that 
we are losing data. We got short files starting at 174h into the GFS run, and 
only got (incomplete) data through 207h.

We have now not received any data on CONDUIT since 11:27 AM CST (1727 UTC) 
today (Wed Feb 20)

Pete



<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.weather.com%2Ftv%2Fshows%2Fwx-geeks%2Fvideo%2Fthe-incredible-shrinking-cold-pool&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570142698&sdata=y3refCa5zQubcuoGwMIaqPHUmKZrip0WirYwUsLQHj8%3D&reserved=0>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>

________________________________
From: conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx> 
<conduit-bounces@xxxxxxxxxxxxxxxx<mailto:conduit-bounces@xxxxxxxxxxxxxxxx>> on 
behalf of Pete Pokrandt <poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>>
Sent: Wednesday, February 20, 2019 11:28 AM
To: Carissa Klemmer - NOAA Federal
Cc: conduit@xxxxxxxxxxxxxxxx<mailto:conduit@xxxxxxxxxxxxxxxx>; 
support-conduit@xxxxxxxxxxxxxxxx<mailto:support-conduit@xxxxxxxxxxxxxxxx>
Subject: [conduit] Large lags on CONDUIT feed - started a week or so ago

Carissa,

We have been feeding CONDUIT using a 5 way split feed direct from 
conduit.ncep.noaa.gov<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fconduit.ncep.noaa.gov&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570152707&sdata=%2FZG7wjkS9jh7h8pc0lrNWcU6W9w%2FzFwGfdd3HT0%2B0XQ%3D&reserved=0>,
 and it had been really good for some time, lags 30-60 seconds or less.

However, the past week or so, we've been seeing some very large lags during 
each 6 hour model suite - Unidata is also seeing these - they are also feeding 
direct from 
conduit.ncep.noaa.gov<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fconduit.ncep.noaa.gov&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570152707&sdata=%2FZG7wjkS9jh7h8pc0lrNWcU6W9w%2FzFwGfdd3HT0%2B0XQ%3D&reserved=0>.

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+idd.aos.wisc.edu<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frtstats.unidata.ucar.edu%2Fcgi-bin%2Frtstats%2Fiddstats_nc%3FCONDUIT%2Bidd.aos.wisc.edu&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570162721&sdata=NLBOKjWG9EfHVBj7A0R6jJA601dOUTS3RIo0lA5RS1c%3D&reserved=0>

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+conduit.unidata.ucar.edu<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frtstats.unidata.ucar.edu%2Fcgi-bin%2Frtstats%2Fiddstats_nc%3FCONDUIT%2Bconduit.unidata.ucar.edu&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570172722&sdata=s%2FnkQz9y1BuE7ZlQMvfeBhBdqgHxcGlTYXDGCnjCXkY%3D&reserved=0>


Any idea what's going on, or how we can find out?

Thanks!
Pete



<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.weather.com%2Ftv%2Fshows%2Fwx-geeks%2Fvideo%2Fthe-incredible-shrinking-cold-pool&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570172722&sdata=w122EutnxtWO8t0UiJoLlS6eCpgsTIU6HKp5FXiH45A%3D&reserved=0>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086  - poker@xxxxxxxxxxxx<mailto:poker@xxxxxxxxxxxx>

_______________________________________________
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<mailto:conduit@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit: 
http://www.unidata.ucar.edu/mailing_lists/<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.unidata.ucar.edu%2Fmailing_lists%2F&data=02%7C01%7Caap1%40psu.edu%7Cf75a98e5c01047c786b108d6981ed7a7%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636863655570182726&sdata=kczuJ9sUa9DaoGZJCltvhivTs5ySVbUhzK8b7az7cGg%3D&reserved=0>
  • 2019 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the conduit archives: