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

[IDD #OKS-541262]: Fwd: Re: 20150120: INPE LDM REQUESTs being blocked on idd.unidata.ucar.edu

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDD #OKS-541262]: Fwd: Re: 20150120: INPE LDM REQUESTs being blocked on idd.unidata.ucar.edu
  • Date: Tue, 27 Jan 2015 15:00:19 -0700
Hi Diogo,

re:
> I'm system administrator of tempestades.org.br (nldm.tempestades.org.br)

Just so you know, we contacted Waldenio to see if he knew who was making
the excessive number of feed REQUESTs for 0.5 degree GFS data (at one time
there were 96 feed REQUESTs active) that was seriously impacting
performance on the real server backend node of our idd.unidata.ucar.edu relay
cluster. Since we had no contact information on file, we were forced to
block the feed REQUESTs so that data flow to other users would not be negatively
impacted.

re:
> and the syntax error in ldmd.conf (REQUEST) was found and corrected:
> 
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f00[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f01[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f02[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f03[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f04[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f05[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f06[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f07[0-9]" idd.unidata.ucar.edu
> REQUEST CONDUIT "gfs.t18z.pgrb2.0p50.f08[0-9]" idd.unidata.ucar.edu

Question:

- Is this listing a portion of the feed REQUESTs that you intend to use,
  or is it a portion of the feed REQUESTs that you were using?

  I ask because these REQUESTs are specific to the 18 UTC run, and this
  suggests that your ldmd.conf file has additional REQUEST lines for other
  model run times.  Unless there is some serious network bandwidth
  limitations on your end, there should be no reason to split the REQUEST
  for a type of product (e.g., 0.5 degree GFS) by forecast hour.

re:
> Could you release from nldm.tempestades.org.br access to
> idd.unidata.ucar.edu?

Question:

- why are (or were) you splitting the CONDUIT feed REQUESTs 10 ways?

  It strikes us that a single REQUEST for all of the forecast
  hours of the 0.5 degree GFS data could be made in a single
  REQUEST, or, if needed a smaller number of REQUESTs.

Comment:

- before we remove the block for the feed REQUEST(s) from your
  machine, we need to examine your ~ldm/etc/ldmd.conf file
  to be certain that there is nothing that will cause problems
  to other users after reactivation

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: OKS-541262
Department: Support IDD
Priority: Normal
Status: Closed