[LDM #QUM-298362]: primary/secondary

Karen,

> The downstream machine makes a couple of separate requests to the upstream
> machines.  It's request lines typically look like this:
> 
> request EXP "multi/MergedReflectivityQC/"       172.16.5.74
> request EXP "multi/MergedReflectivityQC/"      172.16.5.73
> 
> request EXP "satellite/CloudCover/" 172.16.5.74
> request EXP "satellite/CloudCover/" 172.16.5.73
> 
> request EXP "NSE64" 172.16.5.74
> request EXP "NSE64" 172.16.5.73
> 
> but the upstream machines also request data back from it.  The downstream
> machine also produces data that goes back into it's ldm queue and gets
> requested by the upstreams which then share that data out to other nodes.
> 
> But, yes, the upstreams have identical ldmd.conf files.  And I could see
> the data arriving in each of their queues, but not on the downstream
> machine.  Specifically, I've been looking at the MergedReflectivityQC
> products, as that was what we first noticed was missing from our
> processing.  I haven't looked at other products, but I fear they will also
> have missing pieces in the data flow.

Hmm... I"m going to have to think about this.

> As for the individual requests to the upstreams (putting both in primary
> mode), I do seem to be getting all of the data that way as well.
> 
> --
> “Climate is what you expect, weather is what you get."
> -- Robert A. Heinlein
> 
> -------------------------------------------
> address@hidden
> 
> Phone:  405-325-6982
> Cell:   405-834-8559
> INDUS Corporation
> National Severe Storms Laboratory


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: QUM-298362
Department: Support LDM
Priority: Normal
Status: Open