Hi Harry, re: > I am seeing a lot of delays in my UNIWISC feed from > unidata2-new.ssec.wisc.edu. > Can you see any reason for this? Hmm... The UNIWISC products are getting to our top level relay cluster, idd.unidata.ucar.edu, without significant delays. Here is the link for the latency plot for one of our cluster real-server backends: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?UNIWISC+uni18.unidata.ucar.edu But, the same products are not making it to idd.ssec.wisc.edu (aka unidata2-new.ssec.wisc.edu) with the same low latencies: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?UNIWISC+idd.ssec.wisc.edu It seems that all non-locally sourced feeds flowing to idd.ssec.wisc.edu are experiencing high/higher than normal latencies (this does not include the feeds that originate from NOAAPort since idd.ssec.wisc.edu REQUESTs those feeds from the two ingest machines that SSEC maintains). We will need to investigate what may be going on. Since the UNIWISC latencies are low on idd.unidata.ucar.edu, I suggest that you add a redundant feed REQUEST to it while keeping your existing REQUEST(s) to idd.ssec.wisc.edu. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: LSK-706023 Department: Support IDD 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.