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

["Carl Yeksigian (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Yeksigian updated CASSANDRA-11569:
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.8
           Status: Resolved  (was: Patch Available)

+1. Thanks, [~cnlwsu]!

Commited as [04afa2b|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=04afa2bf52ce6f5a534323678defd625dca67336].

> 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
>             Fix For: 3.8
>
>         Attachments: CASSANDRA-11569.patch, CASSANDRA-11569v2.txt, nodeLatency.PNG
>
>
> 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)