[
https://issues.apache.org/jira/browse/CASSANDRA-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363421#comment-14363421
]
Sylvain Lebresne commented on CASSANDRA-8437:
---------------------------------------------
Sorry, I had missed the last update on this and kind of forgot about it.
Regarding the last version, It's probably not a big deal but I wonder if it
wouldn't be better to actually count all mismatches individually rather in
{{SP.fetchRows}}. Probably not a big deal but it just feels a bit more logical
(it's possible I suggested otherwise early on so sorry if that was the case).
> 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.4
>
> 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)
