cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6758) Measure data consistency in the cluster
Date Mon, 24 Feb 2014 13:31:19 GMT

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

Jonathan Ellis commented on CASSANDRA-6758:
-------------------------------------------

That is (one reason) why we took a different approach with CASSANDRA-5351.

> Measure data consistency in the cluster
> ---------------------------------------
>
>                 Key: CASSANDRA-6758
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6758
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jimmy MÃ¥rdell
>            Priority: Minor
>
> Running multi-DC Cassandra can be a challenge as the cluster easily tends to get out-of-sync.
We have been thinking it would be nice to measure how out of sync a cluster is and expose
those metrics somehow.
> One idea would be to just run the first half of the repair process and output the result
of the differencer. If you use Random or the Murmur3 partitioner, it should be enough to calculate
the merkle tree over a small subset of the ring as the result can be extrapolated.
> This could be exposed in nodetool. Either a separate command or perhaps a dry-run flag
to repair?
> Not sure about the output format. I think it would be nice to have one value ("% consistent"?)
within a DC, and also one value for every pair of DC's perhaps?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message