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

Jeff Jirsa resolved CASSANDRA-6758.
-----------------------------------
    Resolution: Fixed

Calling this fixed, as the requirements are mostly done, just by other tickets. 

> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to