Huge number of Mismatchs in the logs

[Mun Dega <mu...@gmail.com>]

I upgraded from 2.1 to 3.11 and started to get huge number of Digest
mismatch errors in the DEBUG log.  I ran a full repair in the cluster but
it did not seem to cut back on these.

My consistency is QUORUM so my guess is this error is on reads but would
this also affect my writes to all replicas if my RF is 3?

DEBUG [ReadRepairStage:1788] 2018-09-01 03:40:41,737 ReadCallback.java:242
- Digest mismatch: org.apache.cassandra.service.DigestMismatchException:
Mismatch for key DecoratedKey(-1046384702160736076,
423042334144313738374438) (6df35a84b4f9c1109342c744b84eead9 vs
ef096894f14a8e2db75ed28396c570d3) at
org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92)
~[apache-cassandra-3.11.2.jar:3.11.2] at
org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233)
~[apache-cassandra-3.11.2.jar:3.11.2] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_51] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_51] at
org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81)
[apache-cassandra-3.11.2.jar:3.11.2] at
org.apache.cassandra.concurrent.NamedThreadFactory$$Lambda$7/343563528.run(Unknown
Source) [apache-cassandra-3.11.2.jar:3.11.2] at
java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]

Ma

Re: Huge number of Mismatchs in the logs

[Felipe Esteves <fe...@b2wdigital.com>]

Hi, I've got the same problem
Upgraded from 2.2.11 to 3.11.3 and since then the DEBUG logs shows this
messages.

Seems to me that after the repair the messages were reduced a little, but
it's still happening.
In my case is a 3-node cluster, RF3, reads and writes with LOCAL_QUORUM

Felipe Esteves

Tecnologia

felipe.esteves@b2wdigital.com <se...@b2wdigital.com>

Tel.: (21) 3504-7162 ramal 57162

Skype: felipe2esteves


Em sáb, 1 de set de 2018 às 01:11, Mun Dega <mu...@gmail.com> escreveu:

> I upgraded from 2.1 to 3.11 and started to get huge number of Digest
> mismatch errors in the DEBUG log.  I ran a full repair in the cluster but
> it did not seem to cut back on these.
>
> My consistency is QUORUM so my guess is this error is on reads but would
> this also affect my writes to all replicas if my RF is 3?
>
> DEBUG [ReadRepairStage:1788] 2018-09-01 03:40:41,737 ReadCallback.java:242
> - Digest mismatch: org.apache.cassandra.service.DigestMismatchException:
> Mismatch for key DecoratedKey(-1046384702160736076,
> 423042334144313738374438) (6df35a84b4f9c1109342c744b84eead9 vs
> ef096894f14a8e2db75ed28396c570d3) at
> org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92)
> ~[apache-cassandra-3.11.2.jar:3.11.2] at
> org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233)
> ~[apache-cassandra-3.11.2.jar:3.11.2] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_51] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_51] at
> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81)
> [apache-cassandra-3.11.2.jar:3.11.2] at
> org.apache.cassandra.concurrent.NamedThreadFactory$$Lambda$7/343563528.run(Unknown
> Source) [apache-cassandra-3.11.2.jar:3.11.2] at
> java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
>
> Ma
>
>
> ------------------------------
>
> Esta mensagem pode conter informações confidenciais e somente o indivíduo
> ou entidade a quem foi destinada pode utilizá-la. A transmissão incorreta
> da mensagem não acarreta a perda de sua confidencialidade. Caso esta
> mensagem tenha sido recebida por engano, solicitamos que o fato seja
> comunicado ao remetente e que a mensagem seja eliminada de seu sistema
> imediatamente. É vedado a qualquer pessoa que não seja o destinatário usar,
> revelar, distribuir ou copiar qualquer parte desta mensagem. Ambiente de
> comunicação sujeito a monitoramento.
>
> This message may include confidential information and only the intended
> addresses have the right to use it as is, or any part of it. A wrong
> transmission does not break its confidentiality. If you've received it
> because of a mistake or erroneous transmission, please notify the sender
> and delete it from your system immediately. This communication environment
> is controlled and monitored.
>
> B2W Digital
>
>
>

--