[jira] [Updated] (CASSANDRA-8437) Track digest mismatch ratio

["Benjamin Lerer (JIRA)" <ji...@apache.org>]

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

Benjamin Lerer updated CASSANDRA-8437:
--------------------------------------
    Attachment: CASSANDRA-8437.txt

The patch extends the Read metrics of the {{StorageProxy}} to allow the computation of the digest mismatch ratio and expose it in nodetool in the info section.

> 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)