Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 1 Jun 2015 17:23:17 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12829903.1431621422000.84332.1433179397238@Atlassian.JIRA>
In-Reply-To: <JIRA.12829903.1431621422000@Atlassian.JIRA>
References: <JIRA.12829903.1431621422000@Atlassian.JIRA>
 <JIRA.12829903.1431621422243@arcas>
Subject: [jira] [Commented] (CASSANDRA-9388) Truncate can (in theory) lead
 to corrupt responses to client or segfault
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567605#comment-14567605 ] 

Aleksey Yeschenko commented on CASSANDRA-9388:
----------------------------------------------

The newly added {{discard}} {{ArrayList}} is not being used by anything. I assume something's not right here.

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