This isn’t really an error and shouldn’t be logged because so few people understand it well enough to find it useful. Some number of digest mismatches are expected if you read as you write. I wouldn’t worry about it unless you’re having a problem.
-- Jeff Jirsa > On Apr 17, 2018, at 12:29 AM, techpyaasa <techpya...@gmail.com> wrote: > > Hi, > > We have recently upgraded our cassandra production cluster(2 datacenters , > each with 6 nodes, 3 groups) from c*-2.1.17 to c*-3.0.15. > > After which we are getting too many exceptions as below. > >> org.apache.cassandra.service.DigestMismatchException: Mismatch for key >> DecoratedKey(-1032881015386111041, 03c099b9959871a9) >> (a613f5fd9fc797b252e26fe9b9b1ed4e vs 15b7d82a9b454f5fd433317f68de435f) >> at >> org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) >> at >> org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:225) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> at >> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:79) >> at java.lang.Thread.run(Thread.java:745) >> > > No hints present /no mutation dropped, but still the above exception is > thrown quite frequently. > > Could someone help us out in finding out the root cause. > > Thanks in advance > TechPyaasa
