[
https://issues.apache.org/jira/browse/CASSANDRA-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-13964:
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.0
3.11.2
3.0.16
Reproduced In: 3.11.1, 3.0.15, 4.0 (was: 3.0.15, 3.11.1, 4.0)
Status: Resolved (was: Patch Available)
The CI was generally good barring a couple of flaky-ish tests which I've
checked are passing locally, so I've committed to 3.0 in
{{58daf1376456289f97f0ef0b0daf9e0d03ba6b81}} and merged to 3.11 and trunk.
> Tracing interferes with digest requests when using RandomPartitioner
> --------------------------------------------------------------------
>
> Key: CASSANDRA-13964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13964
> Project: Cassandra
> Issue Type: Bug
> Components: Local Write-Read Paths, Observability
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Fix For: 3.0.16, 3.11.2, 4.0
>
>
> A {{ThreadLocal<MessageDigest>}} is used to generate the MD5 digest when a
> replica serves a read command and the {{isDigestQuery}} flag is set. The same
> threadlocal is also used by {{RandomPartitioner}} to decorate partition keys.
> So in a cluster with RP, if tracing is enabled the data digest is corrupted
> by the partitioner making tokens for the tracing mutations. This causes a
> digest mismatch on the coordinator, triggering a full data read on every read
> where CL > 1 (or speculative execution/read repair kick in).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
