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

[CONDUIT #EKQ-308585]: GFS data problem

Hi,

re:
> So queue on ldm.dri.edu is 30 GB, which according to your last email
> should be enough. 

Correct.

re:
> Any way to check high latencies upstream from ldm.dri.edu machine?

Plots/lists of a variety of things for machines that are reporting
real-time stats back to us can be found as follows:

Unidata HomePage
https://www.unidata.ucar.edu

  Data -> Operational Status
  https://rtstats.unidata.ucar.edu/rtstats/

    Real-time IDD Statistics -> Statistics by Host
    https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex

The listing in the last page is organized alphabetically by
domain (e.g., .edu, .com, .gov. etc.).  Scroll down to the
section that lists machines at your site that are reporting
real-time stats, and click on the appropriate name.  For
instance:

ldm.dri.edu:
https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?ldm.dri.edu

Like I said in previous replies, NCEP has been having problems with
delivering CONDUIT data with small latencies from one of their top
level sites, and this problem is reflected in the latencies that end-user
sites experience.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: EKQ-308585
Department: Support CONDUIT
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.