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

[IDD #TML-937455]: NEXRAD3 delays



Hi Harry,

re:
> Over the past week I have seen significant delays in the NEXRAD3 feed between
> 0430 and 1230 to both of my feed system (freshair1 and freshair2).    Do you 
> see
> any reason for this on your side?

Not right off.

A quick review of the latencies being reported on freshair1 seem to show
that the CONDUIT latencies are similar to the NEXRAD3 ones.  This may or
may not indicate that there is a problem on our end (reaching the maximum
volume of data that can be sent down the 2 bonded Ethernet interfaces
for the idd.unidata.ucar.edu cluster node that is actually feeding freshair1,
but the problem with this possibility is that you seem to be feeding
redundantly from both idd.unidata.ucar.edu and iddb.unidata.ucar.edu,
and the real server backends of iddb.unidata.ucar.edu are not feeding
many downstreams.

We will have to investigate further on this end to see what may be
happening.  This investigation will have to be delayed, however, since
Mike Schmidt is currently out of the office, and he is the one here
that has the expertise to get to the bottom of the feed delays.

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: TML-937455
Department: Support IDD
Priority: Normal
Status: Open