[
https://issues.apache.org/jira/browse/CASSANDRA-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15848:
----------------------------------------
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/4d1bdb129c3103c51b470b4a008039fe85d7571f
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks, committed to trunk in {{4d1bdb129c3103c51b470b4a008039fe85d7571f}}
There 2 dtest failure, both timeouts, which I couldn't reproduce locally.
> Fully purged static row causes NPE in repaired data tracking
> ------------------------------------------------------------
>
> Key: CASSANDRA-15848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15848
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> During repaired data tracking, if the result of applying the purge function
> to a static row is null, an exception is thrown from RepairedDataInfo. This
> will cause a read exception from the replica and could lead to unavailable
> results if hit on multiple replicas. A workaround is to disable repaired data
> tracking.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
