Re: Digest mismatch

Some more info. From java using the Datastax 4.9.0 driver, I'm selecting an entire table, after about 17 million rows (the table is probably around 150 million rows), I get: com.datastax.oss.driver.api.core.servererrors.ReadFailureException: Cassandra failure during read query at consistency

Re: Cassandra row-cache API

Thanks Jeff, the summary at the end is very insightful - something we also are observing. On a related note, we do observe that the "first N clustering" doesn't exactly behave the way it is documented to. Is it related to this open ticket CASSANDRA-8646

Re: Cassandra row-cache API

Sometime around 2.0 or 2.1, it was changed from a "partition cache" to a "head of the partition cache", where "head of the partition" means "first N clustering". The reason individual rows are "hard" is the same reason most things with Cassandra caching and consistency are "hard" - a clustering /

Cassandra row-cache API

Hello All, Wondering if anyone has tried to modify the row-cache API to use both the partition key and the clustering keys to convert the row-cache, which is really a partition cache today, into a true row-cache? This might help with broader adoption of row-cache for use-cases with large partition

Re: Digest mismatch

Thanks all for the help on this.  I've changed all my writes to LOCAL_QUORUM, and same with reads.  Under a constant load of doing writes to a table and reads from the same table, I'm still getting the: DEBUG [ReadRepairStage:372] 2020-12-14 09:36:09,002 ReadCallback.java:244 - Digest mismatch