cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11569) Track message latency across DCs
Date Wed, 18 May 2016 21:02:13 GMT

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

Chris Lohfink commented on CASSANDRA-11569:
-------------------------------------------

bq. I will got an error as the crosslatency is too large

What error?

I could not reproduce anything. I added some tests to make it easier to try different latencies
as well (v2 patch with minor refactoring for easier testing).

> 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, CASSANDRA-11569v2.txt
>
>
> 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)

Mime
View raw message