cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-8437) Track digest mismatch ratio
Date Thu, 16 Apr 2015 19:44:59 GMT

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

Benjamin Lerer edited comment on CASSANDRA-8437 at 4/16/15 7:44 PM:
--------------------------------------------------------------------

Thanks [~slebresne]. I do not think we ever discussed the second alternative which is, I agree,
the one that makes the most sense.


was (Author: blerer):
Thanks [~slebresne]. I do not think we ever discussed the second alternative which is I agree
the one that makes the most sense.

> 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.5
>
>         Attachments: CASSANDRA-8437-V2.txt, 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