cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8437) Track digest mismatch ratio
Date Tue, 20 Jan 2015 17:44:36 GMT

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

Brandon Williams commented on CASSANDRA-8437:
---------------------------------------------

Well, that's trivial to compute between netstats/cfstats, but netstats seems like the more
logical place to include it so you only need one command for all your RR inquiries.

> Track digest mismatch ratio
> ---------------------------
>
>                 Key: CASSANDRA-8437
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8437
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Benjamin Lerer
>            Priority: Minor
>             Fix For: 2.1.3
>
>         Attachments: CASSANDRA-8437.txt
>
>
> I don't believe we track how often read results in a digest mismatch but we should since
that could directly impact read performance in practice.
> Once we have that data, it might be that some workloads (write heavy most likely) ends
up with enough mismatches that going to the data read is more efficient in practice. What
we do about it it step 2 however, but getting the data is easy enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message