You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/05/14 18:38:59 UTC

[jira] [Updated] (CASSANDRA-9388) Truncate can (in theory) lead to corrupt responses to client or segfault

     [ https://issues.apache.org/jira/browse/CASSANDRA-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benedict updated CASSANDRA-9388:
--------------------------------
    Attachment: 9388.txt

Basically we don't wait for reads to complete before freeing the data in the exceptional case of truncate. I have merged the two paths, so that they follow the same protocol (of waiting).

> 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: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 2.1.x
>
>         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)