You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/12/08 10:47:12 UTC

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

Sylvain Lebresne created CASSANDRA-8437:
-------------------------------------------

             Summary: 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


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)