Re: Understanding which table had digest mismatch

2021-02-27 Thread Gil Ganz
Eric - I understand, thing is repairs are causing issues and I would like to have the option to only run them on the tables that really need that. Kane - Thanks, good idea, I will check that metric. On Fri, Feb 26, 2021 at 12:07 AM Kane Wilson wrote: > You should be able to use the Table

Re: Understanding which table had digest mismatch

2021-02-25 Thread Kane Wilson
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

Re: Understanding which table had digest mismatch

2021-02-25 Thread Erick Ramirez
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! >

Understanding which table had digest mismatch

2021-02-25 Thread Gil Ganz
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,