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.
Celia, Yes, the times are latency for a product. You have a machine "clamp" that is feeding from both thelma.ucar.edu and f5.aos.wisc.edu as you see here: http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+clamp.rap.ucar.edu You also see that alost the entire volume yopu are receiving is coming via thelma, and very little via f5: http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?CONDUIT+clamp.rap.ucar.edu I suspect that your queue isn't large enough to hold 1 hours worth of data, and that periodically, you receive an old product from f5 that you already received from thelma, but has since been scoured out of your queue- so you receive it a second time from the redundant feeder. You can use the ldm program "pqmon" to show you the age of the oldest product in your queue. If this is falling below 1 hour (3600 seconds) and you are feeding from more than 1 host, you could receive a product that you had previously received but has since been scoured out of your queue to make room for new data. Steve Chiswell Unidata User Support >From: Celia Chen <address@hidden> >Organization: UCAR/Unidata >Keywords: 200501062146.j06Lkiv2014808 >Dear support, > >Under CONDUIT, in the "RTSTATS Index by Site IDD Topology Feed List", it >I saw the following: > >level.rap.ucar.edu [512 seconds] > > rasp.rap.ucar.edu [2208 seconds] > >clamp.rap.ucar.edu [3880 seconds] > > rasp.rap.ucar.edu [3886 seconds] > level.rap.ucar.edu ** Redundant loop ** > >Could you tell me if the number of seconds in [] are >latency in time? If so, what could cause the large latency shown >on some of our ldm hosts that get the CONDUIT feed? > > >Thanks in advance. > >Celia > -- 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.