[
https://issues.apache.org/jira/browse/CASSANDRA-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-9388:
-----------------------------------------
Fix Version/s: (was: 2.1.x)
2.2.0 rc1
2.1.6
> Truncate can (in theory) lead to corrupt responses to client or segfault
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-9388
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9388
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 2.1.6, 2.2.0 rc1
>
> Attachments: 9388.txt
>
>
> Noticed this while searching for another problem. I don't have a unit test
> exhibiting it, as it would be non-trivial to add (needs a high rate burn test
> of writes, reads, truncates and non-snapshotted CFs). We can perhaps file a
> follow-up ticket to address that, however the kitchen sink tests will
> hopefully cover this ground.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
