cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9388) Truncate can (in theory) lead to corrupt responses to client or segfault
Date Mon, 01 Jun 2015 14:51:17 GMT

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

Aleksey Yeschenko updated CASSANDRA-9388:
-----------------------------------------
    Reviewer: Aleksey Yeschenko

> 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.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)

Mime
View raw message