cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-8437) Track digest mismatch ratio
Date Sat, 12 Sep 2015 13:50:46 GMT


Aleksey Yeschenko updated CASSANDRA-8437:
    Fix Version/s:     (was: 2.1.x)

> Track digest mismatch ratio
> ---------------------------
>                 Key: CASSANDRA-8437
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Benjamin Lerer
>            Priority: Minor
>         Attachments: CASSANDRA-8437-V2.txt, CASSANDRA-8437-V3.txt, CASSANDRA-8437-V4.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

View raw message