There are likely two log configs - one for debug.log and one for system.log.
Disable the debug.log one, or change org.apache.cassandra.service to log at
INFO instead
Nobody needs to see every digest mismatch and that someone thought this was a
good idea is amazing to me. Someone should jira th
Thanks Shalom, I know why these read repairs are happening, and they will
continue to happen for some time, even if I will run a full repair.
I would like to disable these warning messages.
On Sun, Mar 8, 2020 at 10:19 AM Shalom Sagges
wrote:
> Hi Gil,
>
> You can run a full repair on your clust
Hi Gil,
You can run a full repair on your cluster. But if these messages come back
again, you need to check what's causing these data inconsistencies.
On Sun, Mar 8, 2020 at 10:11 AM Gil Ganz wrote:
> Hey all
> I have a lot of debug message about read repairs in my debug log :
>
> DEBUG [ReadR
Hey all
I have a lot of debug message about read repairs in my debug log :
DEBUG [ReadRepairStage:346] 2020-03-08 08:09:12,959 ReadCallback.java:242 -
Digest mismatch:
org.apache.cassandra.service.DigestMismatchException: Mismatch for key
DecoratedKey(-28476014476640,
000400871130303a3
