[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: Wed, 28 Jan 2015 13:00:52 -0700
Hi Diogo,

re: what REQUESTs are you now wanting to use?

> The feed REQUESTs that we intend to use for 00UTC, 12UTC and 18UTC. We
> have limitation network bandwidth, that's we splitted REQUESTs.

The number of REQUEST lines in the ldmd.conf file you included is 19
which is still excessive, here is why:

Each REQUEST results in the creation of an upstream LDM server (ldmd)
on the machine to which the REQUESTs are made.  These processes use
system resources even when they are not active (meaning that no data
is flowing).  I understand the attempt to split the REQUESTs, but
you have taken this process too far.  The reason I say this is when
the REQUESTs for a particular forecast run (e.g., 0Z, 12Z or 18Z)
are actively moving data, the other ones will have nothing to move,
but they will still be using resources on the upstream feeder(s).

If your intention is to use the same set of REQUEST lines for access to
idd.unidata.ucar.edu, we will not remove the block that we implemented.
We will, however, remove the block if you change your REQUESTs to the
following:

REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f00[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f01[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f02[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f03[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f04[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f05[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f06[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f07[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f08[0-9]" idd.unidata.ucar.edu

This reorganization reduces the number of feed REQUESTs and corresponding
upstream server processes from 19 to 9.

Also, we recommend that you make this set of REQUESTs to idd.cptec.inpe.br
for redundancy.  What I mean is that your ldmd.conf should look like:

#######################################################
# 0.5 deg GFS from CPTEC
#######################################################
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f00[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f01[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f02[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f03[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f04[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f05[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f06[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f07[0-9]" idd.cptec.inpe.br
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f08[0-9]" idd.cptec.inpe.br

#######################################################
# 0.5 deg GFS from Unidata
#######################################################
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f00[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f01[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f02[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f03[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f04[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f05[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f06[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f07[0-9]" idd.unidata.ucar.edu
REQUEST CONDUIT "gfs.t(00|12|18)z.pgrb2.0p50.f08[0-9]" idd.unidata.ucar.edu

Please let us know if you are willing to make this change.

re:
> I'm sorry my poor english.

No worries.  Your English is MUCH better than my Portuguese :-)

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