Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 17 May 2016 07:35:13 +0000 (UTC)
From: "stone (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12958592.1460578468000.207180.1463470513103@Atlassian.JIRA>
In-Reply-To: <JIRA.12958592.1460578468000@Atlassian.JIRA>
References: <JIRA.12958592.1460578468000@Atlassian.JIRA> <JIRA.12958592.1460578468647@arcas>
Subject: [jira] [Commented] (CASSANDRA-11569) Track message latency across
 DCs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 May 2016 07:35:14 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286184#comment-15286184 ] 

stone commented on CASSANDRA-11569:
-----------------------------------

Have made test on this patch?
Actually I have 2 DataCenter,client is in DC1,
when there is no latency between DC2 and DC1.
and I set 10 ms/100ms latency,there is no change about the value of CrossNodeLatency

> Track message latency across DCs
> --------------------------------
>
>                 Key: CASSANDRA-11569
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11569
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>         Attachments: CASSANDRA-11569.patch
>
>
> Since we have the timestamp a message is created and when arrives, we can get an approximate time it took relatively easy and would remove necessity for more complex hacks to determine latency between DCs.
> Although is not going to be very meaningful when ntp is not setup, it is pretty common to have NTP setup and even with clock drift nothing is really hurt except the metric becoming whacky.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)