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

[LDM #KGJ-740033]: Problems with LDM



Hi Peter,

Please try the follow:

change your REQUEST lines from:

REQUEST ANY-GPS-MCIDAS ".*" idd.unidata.ucar.edu
REQUEST ANY-GPS-MCIDAS ".*" idd.tamu.edu
REQUEST MCIDAS ".*" idd.aos.wisc.edu
REQUEST MCIDAS ".*" idd.ssec.wisc.edu
REQUEST GPS ".*" suomildm1.cosmic.ucar.edu
REQUEST GPS ".*" idd.unidata.ucar.edu

to:

REQUEST ANY-CONDUIT-NEXRAD2-GPS-MCIDAS ".*" idd.tamu.edu
REQUEST NEXRAD2 ".*" idd.tamu.edu
REQUEST CONDUIT "([09]$)" idd.tamu.edu
REQUEST CONDUIT "([18]$)" idd.tamu.edu
REQUEST CONDUIT "([27]$)" idd.tamu.edu
REQUEST CONDUIT "([36]$)" idd.tamu.edu
REQUEST CONDUIT "([45]$)" idd.tamu.edu

REQUEST ANY-CONDUIT-NEXRAD2-GPS-MCIDAS ".*" idd.unidata.ucar.edu
REQUEST NEXRAD2 ".*" idd.unidata.ucar.edu
REQUEST CONDUIT "([09]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([18]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([27]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([36]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([45]$)" idd.unidata.ucar.edu

REQUEST MCIDAS ".*" idd.aos.wisc.edu
REQUEST MCIDAS ".*" idd.ssec.wisc.edu
REQUEST GPS ".*" suomildm1.cosmic.ucar.edu
REQUEST GPS ".*" idd.unidata.ucar.edu

We came up with this suggesting after reviewing the latencies
that are being reported by ldmingest02:

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

  Projects -> Internet Data Distribution
  http://www.unidata.ucar.edu/projects/index.html#idd

    IDD Current Operational Status
    http://www.unidata.ucar.edu/software/idd/rtstats/

      Statistics by Host
      http://www.unidata.ucar.edu/cgi-bin/rtstats/siteindex

        ldmingest02.nwc.ou.edu [6.10.1]
        
http://www.unidata.ucar.edu/cgi-bin/rtstats/siteindex?ldmingest02.nwc.ou.edu

The latencies for the very low volume IDS|DDPLUS are unacceptably
high.  The theory here is that your REQUESTs for everything except
the low volume UNIWISC (aka MCIDAS) and GPS feeds are exceeding some
unknown threshold.  FYI: the current volume in the IDD feeds available
averages between 11 and 15 GB/hr ** average ** with peaks up to 22 GB/hr.

If splitting the feeds suggested above works, you may have to consider
splitting your NEXRAD2 feed as well.

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: KGJ-740033
Department: Support LDM
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.