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] [Commented] (CASSANDRA-8437) Track digest mismatch ratio
Date Thu, 16 Apr 2015 16:01:59 GMT

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

Benjamin Lerer commented on CASSANDRA-8437:
-------------------------------------------

[~slebresne] I just wanted to double check before creating the new patch. Are you sure about
your last comment? It seems to conflit with the previous one.
The patch need to be modified anyway, as it will produce an error if sombody try to use nodetool
with an older 2.1 release (similar to CASSANDRA-8796).


> 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