Re: [ldm-users] question about primary and secondary data transfer

  • To: Karen Cooper - NOAA Affiliate <karen.cooper@xxxxxxxx>
  • Subject: Re: [ldm-users] question about primary and secondary data transfer
  • From: Greg Trotter <gtrotter@xxxxxxxxxx>
  • Date: Mon, 15 Jan 2018 15:08:22 +0000
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=gtrotter@xxxxxxxxxx;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
Yeah, that’s what I think is happening.

Steve pointed me in a direction of some code to modify, I will see if that can 
do what I need. I agree, what you describe would be a very useful feature.

From: Karen Cooper - NOAA Affiliate [mailto:karen.cooper@xxxxxxxx]
Sent: Friday, January 12, 2018 10:43 PM
To: Greg Trotter <gtrotter@xxxxxxxxxx>
Cc: ldm-users@xxxxxxxxxxxxxxxx
Subject: Re: [ldm-users] question about primary and secondary data transfer

Hi Greg,

I have a feeling it's trying to get data from both sources and trying to 
balance between them.

It would be nice if you could select a preferred source and a secondary source 
that you only go to if your preferred source goes down for a specified amount 
of time.

On Fri, Jan 12, 2018 at 1:43 PM, Greg Trotter 
<gtrotter@xxxxxxxxxx<mailto:gtrotter@xxxxxxxxxx>> wrote:
I have an LDM server that is connected to two upstreams – one is my NOAAPORT 
ingester on my local network, and one is a backup site at a remote location. I 
have both listed in my ldmd.conf, with the local server listed first, and the 
request patterns are identical.

Looking at the queue, it looks like all is well – the origin on all the 
products is from our local NOAAPORT ingest server. If I look at the network 
traffic on that server, however, I see a lot of data coming in from the remote 
server – almost as much as we are bringing in from the local server. I theorize 
that the downstream doesn’t see it locally, and requests it from the remote 
upstream, but by the time it arrives, it’s come in from the local upstream? I 
can’t find any other reason that we’d be having that much traffic from an 
upstream LDM that never appears as an origin for the products in our queue.

Is there something I am doing wrong? Clearly, I’d prefer not to use that much 
bandwidth if we don’t have to. Is there a way to have it only hit the remote 
upstream if the local is unavailable?

Here’s the relevant part of my ldmd.conf:


REQUEST ANY     ".*"    <IP of local noaaport ingester>
REQUEST ANY     ".*"    <IP of remote noaaport ingester>

Greg Trotter
System Administrator
Weather Decision Technologies, Inc
201 David L Boren Blvd Suite 270
Norman, Oklahoma 73072


_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/



--
“The presence of those seeking the truth is infinitely to be preferred to the 
presence of those who think they’ve found it."
 -- Terry Prachett

-------------------------------------------
Karen.Cooper@xxxxxxxx<mailto:Karen.Cooper@xxxxxxxx>

Phone#:  405-325-6456
Cell:   405-834-8559
National Severe Storms Laboratory
  • 2018 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: