Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Nov 2015 09:41:11 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12914631.1447971114000.157699.1448271671551@Atlassian.JIRA>
In-Reply-To: <JIRA.12914631.1447971114000@Atlassian.JIRA>
References: <JIRA.12914631.1447971114000@Atlassian.JIRA>
 <JIRA.12914631.1447971114689@arcas>
Subject: [jira] [Commented] (CASSANDRA-10740) Incorrect condition causes
 cleanup of SSTables which might not need it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcus Eriksson commented on CASSANDRA-10740:
---------------------------------------------

Have not looked too closely, but testCleanupWithNewToken might be a candidate

> Incorrect condition causes cleanup of SSTables which might not need it
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-10740
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10740
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jakub Janecek
>             Fix For: 2.1.x
>
>         Attachments: trunk-10740.txt
>
>
> We needed to perform cleanup of SSTables in our production cluster but found out that it would take several months. Together with my colleague [~JiriHorky] we have pinpointed the issue to method CompactionManager.needsCleanup which incorrectly marks almost all SSTables as the ones needing the cleanup even though that might not be true. I am attaching a patch which should be applicable from version 2.x forward (this is the version we would need it in).
> To explain the problem, the last condition in the cycle that checks whether the next key in the SSTable after the current checked range is NOT contained in the next range falsely marks SSTable as necessary to have cleanup even though it might be contained in some other range. The correct condition (which is actully described in the comment) is to check whether the next key in the SSTable after the current range is less than or equal to the "left" key of the next range (assuming that the left key is exclusive which is described in another comment of the same method).
> Is our patch and reasoning correct?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)