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.
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.
Hi Pete, Quick question: how are you computing these latencies? More specifically, how do you determine which conduit machine the data is coming from? The reason I ask is because I am not seeing any sends of product from conduit2 in the last several days of logs both to our local conduit1 machine and to any distant end users. Also, we have isolated what is likely the issue and will have our team take a closer look in the morning. I'm hopeful they'll be able to resolve this soon. Thanks! Jesse On Mon, Aug 30, 2021 at 5:24 PM Anne Myckow - NOAA Federal < anne.myckow@xxxxxxxx> wrote: > Pete, > > Random aside, can you please update your doco to say that Dataflow's email > list is now nco.dataflow@xxxxxxxx ? I'm CC'ing it here. That other email > address is going to get turned off within the next year. > > Thanks, > Anne > > On Wed, Aug 18, 2021 at 4:02 PM Pete Pokrandt <poker@xxxxxxxxxxxx> wrote: > >> 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 >> >> >> >> From >> https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?conduit.unidata.ucar.edu >> (latencies >> at Unidata) >> >> >> >> 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 >> >> >> >> >> >> <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 >> > > > -- > Anne Myckow > Dataflow Team Lead > NWS/NCEP/NCO > -- Jesse Marks Dataflow Analyst NCEP Central Operations 678-896-9420
conduit archives: