You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "stone (JIRA)" <ji...@apache.org> on 2016/05/17 07:35:13 UTC

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

    [ 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)