You should be able to use the Table metric ReadRepairRequests to determine
which table has read repairs occuring (fairly sure it's present on 3.11.
See
https://cassandra.apache.org/doc/latest/operating/metrics.html#table-metrics
Cheers,
Kane
raft.so - Cassandra consulting, support, and managed se
Volumes die, get corrupted, etc. There may come a time when you have to
destroy the volume and re-create it from a snapshot, or launch a new empty
volume and re-stream the data from replicas (using the replace boot flags)
On Thu, Feb 25, 2021 at 1:17 PM Erick Ramirez
wrote:
> It really depends
It really depends on how you've set up your Kubernetes cluster. For example
if you're using the k8ssandra (https://k8ssandra.io/) with persistent
volumes, the cass-operator should launch a new pod automatically and mount
the same volume to bring the C* node back online.
But it really depends on se
Unfortunately, you won't be able to work it out just based on that debug
message. The only suggestion I have is to run repairs regularly. Cheers!
>
Hey
I'm running cassandra 3.11.9 and I have a lot of messages like this:
DEBUG [ReadRepairStage:2] 2021-02-25 16:41:11,464 ReadCallback.java:244 -
Digest mismatch:
org.apache.cassandra.service.DigestMismatchException: Mismatch for key
DecoratedKey(4059620144736691554,
000455f1134b616e63656
