I’m running into a situation where I’m seeing a lot of Digest errors in the
debug log. I looked at this post:
http://stackoverflow.com/questions/39765813/datastax-mismatch-for-key-issue and
verified that read_repair_chance is set to 0. We are using
DateTieredCompactionStrategy for our time series tables. Can I get some
pointers on how to track this down?
DEBUG [ReadRepairStage:25] 2017-02-14 17:45:03,256 ReadCallback.java:235 -
Digest mismatch:
org.apache.cassandra.service.DigestMismatchException: Mismatch for key
DecoratedKey(-1025043841859687448,
003e2f66736d732f696e746572616374696f6e732f627275696e732d36393564363866382d633935392d343737622d623230342d656637366533646465616535000008000000000000000000)
(d41d8cd98f00b204e9800998ecf8427e vs dabf6fac8cf82262b31514aa719434b7)
at
org.apache.cassandra.service.DigestResolver.resolve(DigestResolver.java:85)
~[apache-cassandra-3.9.0.jar:3.9.0]
at
org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:226)
~[apache-cassandra-3.9.0.jar:3.9.0]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_111]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Regards,
DHRUVA GOPAL
sr. MANAGER, ENGINEERING
REPORTING, ANALYTICS AND BIG DATA
+1 408.325.2011 WORK
+1 408.219.1094 MOBILE
UNITED STATES
dhruva.go...@aspect.com<mailto:dhruva.go...@aspect.com>
aspect.com<http://www.aspect.com/>
[escription: http://webapp2.aspect.com/EmailSigLogo-rev.jpg]
This email (including any attachments) is proprietary to Aspect Software, Inc.
and may contain information that is confidential. If you have received this
message in error, please do not read, copy or forward this message. Please
notify the sender immediately, delete it from your system and destroy any
copies. You may not further disclose or distribute this email or its
attachments.
