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

20030729: NCDC on IDD/CONDUIT (cont.)

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: 20030729: NCDC on IDD/CONDUIT (cont.)
  • Date: Tue, 29 Jul 2003 14:32:56 -0600
>From: "Alan Hall" <address@hidden>
>Organization: NOAA/NCDC
>Keywords: 200307071353.h67DrOLd016914 IDD NCDC

Alan,

re: Are you having problems with atm

>No no problems that I am aware of, but just in case...

OK.

>Also, it seems I remember something about LDM 6 that you didn't have to do the
>failover script, but just request from both ldm servers.  Is that true?

One can setup a PRIMARY feed request to one machine and an ALTERNATE
feed request to a different machine.  The PRIMARY request should be to
the machine that is expected to be able to provide the data the
fastest.  The data in the PRIMARY feed will be sent without asking the
client (the downstream machine) if it wants the product.  The ALTERNATE
server will ask the client if it wants each product.  If the client
answers yes, then the product is sent in one chunk.  If the answer is
no, then no data is sent.  This is not quite the same as having a
failover script running, but it does provide for redundancy since data
will come from the machine that does not go down.

Tom