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

[TIGGE #BGR-338705]: A problem when perform LDM tests

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [TIGGE #BGR-338705]: A problem when perform LDM tests
  • Date: Fri, 20 Jul 2007 12:35:25 -0600
Hi YangXin,

re: I suggest that it is time to switch to use of port 388 exclusively
> OK.

Whenever you are ready...

re: latencies being reported for products injected on tigge-ldm.cma.gov.cn have 
a
baseline of approx. 900 seconds

> I have checked my LDM Server tigge-ldm.cma.gov.cn, the time for this server 
> is set
> to BST (London Time), the hour is GMT+1, the minute is the same as the 
> standard time.

I am a bit worried about your clock being set to a timezone that is different 
from
where you actually are.  I will touch base with others here in Unidata to see 
if this
is a potential problem.

> Because we have a NTP daemon running on each node to control the time 
> synchronization,
> the clock should be very close to standard time and it really is the case.

OK, but I can not understand the high (~900 second) baseline for the latencies 
for
products injected on tigge-ldm.cma.gov.cn, and I do know that this can and will 
be
a problem when downstreams reconnect after remaking their LDM queues.

> Before switching to port 388, I'd like to try one more test in another node 
> whose
> physical configuration is similar to "tigge-ldm.cma.gov.cn" node. You don't 
> need to
> change anything, I will simply stop current test LDM Server, and configure 
> another one
> in the new node, the IP address will be kept the same. 

OK.

> Then I'll have a new test LDM Server with the latest version of LDM and a 
> larger PQ.
> Also, I'd like to use TIGGE-Scripts to insert data instead of REQUESTing data 
> from an upper-stream.
> Hopefully, the latency will reduce to a normal level. If it would be true, 
> then the latency
> problem probably come from somewhere else related to my LDM Server.

OK.  I am leaving yakov's setup to request data.

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: BGR-338705
Department: Support IDD TIGGE
Priority: Normal
Status: Closed