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

Re: [Ncep.list.pmb-dataflow] Large lags on CONDUIT feed - started a week or so ago



Hi Pete,

As of yesterday we failed almost all of our applications to our site in Boulder (meaning away from CONDUIT). Have you noticed an improvement in your speeds since yesterday afternoon? If so this will give us a clue that maybe there's something interfering on our side that isn't specifically CONDUIT, but another app that might be causing congestion. (And if it's the same then that's a clue in the other direction.)

Thanks,
Anne

On Mon, Apr 1, 2019 at 3:24 PM Pete Pokrandt <address@hidden> wrote:
The lag here at UW-Madison was up to 1200 seconds today, and that's with a 10-way split feed. Whatever is causing the issue has definitely not been resolved, and historically is worse during the work week than on the weekends. If that helps at all.

Pete


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



From: Anne Myckow - NOAA Affiliate <address@hidden>
Sent: Thursday, March 28, 2019 4:28 PM
To: Person, Arthur A.
Cc: Carissa Klemmer - NOAA Federal; Pete Pokrandt; _NCEP.List.pmb-dataflow; address@hidden; address@hidden
Subject: Re: [Ncep.list.pmb-dataflow] Large lags on CONDUIT feed - started a week or so ago
 
Hello Art,

We will not be upgrading to version 6.13 on these systems as they are not robust enough to support the local logging inherent in the new version.

I will check in with my team on if there are any further actions we can take to try and troubleshoot this issue, but I fear we may be at the limit of our ability to make this better.

I’ll let you know tomorrow where we stand. Thanks.
Anne

On Mon, Mar 25, 2019 at 3:00 PM Person, Arthur A. <address@hidden> wrote:

Carissa,


Can you report any status on this inquiry?


Thanks...          Art


Arthur A. Person
Assistant Research Professor, System Administrator
Penn State Department of Meteorology and Atmospheric Science
email:  address@hidden, phone:  814-863-1563




From: Carissa Klemmer - NOAA Federal <address@hidden>
Sent: Tuesday, March 12, 2019 8:30 AM
To: Pete Pokrandt
Cc: Person, Arthur A.; address@hidden; address@hidden; _NCEP.List.pmb-dataflow
Subject: Re: Large lags on CONDUIT feed - started a week or so ago
 
Hi Everyone

I’ve added the Dataflow team email to the thread. I haven’t heard that any changes were made or that any issues were found. But the team can look today and see if we have any signifiers of overall slowness with anything. 

Dataflow, try taking a look at the new Citrix or VM troubleshooting tools if there are any abnormal signatures that may explain this. 

On Monday, March 11, 2019, Pete Pokrandt <address@hidden> wrote:
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


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



From: Person, Arthur A. <address@hidden>
Sent: Monday, March 11, 2019 3:45 PM
To: Holly Uhlenhake - NOAA Federal; Pete Pokrandt
Cc: address@hidden; address@hidden
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:  address@hidden, phone:  814-863-1563




From: address@hidden <address@hidden> on behalf of Holly Uhlenhake - NOAA Federal <address@hidden>
Sent: Thursday, February 21, 2019 12:05 PM
To: Pete Pokrandt
Cc: address@hidden; address@hidden
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 <address@hidden> wrote:
Just FYI, data is flowing, but the large lags continue.


Pete


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



From: address@hidden <address@hidden> on behalf of Pete Pokrandt <address@hidden>
Sent: Wednesday, February 20, 2019 12:07 PM
To: Carissa Klemmer - NOAA Federal
Cc: address@hidden; address@hidden
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


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



From: address@hidden <address@hidden> on behalf of Pete Pokrandt <address@hidden>
Sent: Wednesday, February 20, 2019 11:56 AM
To: Carissa Klemmer - NOAA Federal
Cc: address@hidden; address@hidden
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


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



From: address@hidden <address@hidden> on behalf of Pete Pokrandt <address@hidden>
Sent: Wednesday, February 20, 2019 11:28 AM
To: Carissa Klemmer - NOAA Federal
Cc: address@hidden; address@hidden
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, 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.




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

Thanks!
Pete


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

_______________________________________________
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: http://www.unidata.ucar.edu/mailing_lists/


--
Carissa Klemmer
NCEP Central Operations
IDSB Branch Chief
301-683-3835

_______________________________________________
Ncep.list.pmb-dataflow mailing list
address@hidden
https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.pmb-dataflow
--
Anne Myckow
Lead Dataflow Analyst
NOAA/NCEP/NCO
301-683-3825


--
Anne Myckow
Lead Dataflow Analyst
NOAA/NCEP/NCO
301-683-3825