NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
On Thu, 29 Apr 2010, Peter Laws wrote:
On 04/29/10 11:03, Gilbert Sebenste wrote:this occurs, but the bottom line is, no worries: you are fine. If you have a backup, I know exactly why: the latency of the feed is pretty much equal across the two servers you are feeding from, and the LDM is bouncing back and forth between them. I've been asking to have that stopped, but that would apparently cause more problems than not.OK. That's exactly the case since we have two identical systems and the downstreams point to both.
In that case, you really should use slightly different feed requests to keep LDM from bouncing back and forth. For example
REQUEST EXP upstream ".*" REQUEST EXP upstream2 "(.*)" daryl
ldm-users archives: