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

[LDM #CCJ-668460]: Question about behavior of primary/secondary request lines

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: [LDM #CCJ-668460]: Question about behavior of primary/secondary request lines
  • Date: Wed, 09 Nov 2016 12:29:43 -0700
Ryan,

> Does LDM still employ the primary/secondary mechanism for getting data from
> two different upstream LDMs?

Yes.

> My assumption is that as long as the request
> lines are identical in ldmd.conf (with the exception of the upstream host)
> LDM will treat the first entry as primary and the second entry as secondary

Correct -- at least initially.

> and it will not spin up both as simultaneous active threads.

Actually, every REQUEST entry will result in a downstream LDM child process.
Initially, the process resulting from the first of two identical REQUEST entries
for the same data will be in primary transfer mode and the process resulting
from the second REQUEST will be in alternate transfer mode. The two processes
will switch their modes, however, as necessary in order for the best connection
to be in primary mode and the worst connection to be in alternate mode.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: CCJ-668460
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.