[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #ISJ-658184]: NIMAGE feed - big lags from idd.unidata starting ~16 UTC Monday August 5?

Hi Pete,

re:
> FYI, we're still seeing a bit of a bump in latencies on the NIMAGE
> feed at times. Not there for the SATELLITE feed. Strange, since both
> are ultimately originating from iddb or iddc - but the SATELLITE feed
> takes a hop through hera.aos.wisc.edu
> 
> SATELLITE is iddb|iddc.unidata.ucar.edu -> hera.aos.wisc.edu -> 
> idd.aos.wisc.edu -> idd1|idd2.aos.wisc.edu
> 
> NIMAGE is iddb|iddc.unidata.ucar.edu -> idd-agg.aos.wisc.edu -> 
> idd1|idd2.aos.wisc.edu

We have no explanation for why the latencies you are experiencing in
your NIMAGE feed are so high, sorry.

We do have a recommendation for a test:

Add REQUEST(s) for NIMAGE on hera; comment out REQUESTs for NIMAGE
on your cluster aggregator; add a REQUEST for NIMAGE to hera
in place of the REQUESTs for NIMAGE to iddb/iddc; restart the LDMs
on both hera and on your cluster aggregator.

Why?  If the latencies drop to expected low levels, the problem is
likely due to some sort of resource constraint on your cluster
aggregator.  If the latencies don't change, we will have to
continue trying to figure out what is going on.

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: ISJ-658184
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.