Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

arnulf.hanauer_193730 avatar image
arnulf.hanauer_193730 asked ·

Is it possible to determine the keyspace and/or table in a digest mismatch log message?

I have many Digest mismatch messages in my debug.log and I know this typically happens during a Read repair process but the log message typically does not refer to a Keyspace nor a Table which has caused the Read repair to be initiated.

Sample:

DEBUG [ReadRepairStage:42] 2020-12-01 12:43:59,397 ReadCallback.java:244 - Digest mismatch:
org.apache.cassandra.service.DigestMismatchException: Mismatch for key DecoratedKey(5316686551650299872, 0000000670b33dd0) (6d6d385d0619780143abdd514670af43 vs 52e0d02214bde56a28d3729f9d6448b8)

Is it possible from the log message above to track the read repair back to a specific keyspace and/or tables?

read repair
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered ·

Unfortunately, no. It isn't possible to deduce the inconsistent table from the digest mismatch message logged.

There isn't enough information in that debug message to extract that level of detail. Cheers!

Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.