Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 Jun 2014 06:36:24 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12722195.1403091497197.35049.1403591784768@arcas>
In-Reply-To: <JIRA.12722195.1403091497197@arcas>
References: <JIRA.12722195.1403091497197@arcas>
Subject: [jira] [Updated] (CASSANDRA-7414) After cleanup we can end up with
 non-compacting high level sstables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcus Eriksson updated CASSANDRA-7414:
---------------------------------------

    Attachment: 0001-Include-high-level-sstables-in-lower-level-compactio-v2.patch

bq. getOverlappingStarvedSSTables: you can pull calculating min/max boundary out of the loop.
The loop will only be entered for the highest level which has sstables (and has not been compacted for a long time), so we always at most calculate min/max once

attaching v2 which addresses the other comments

> After cleanup we can end up with non-compacting high level sstables
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-7414
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7414
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Minor
>         Attachments: 0001-Include-high-level-sstables-in-lower-level-compactio-v2.patch, 0001-Include-high-level-sstables-in-lower-level-compactio.patch
>
>
> If we run cleanup (or increase sstable size) on a node with LCS, we could end up with a bunch of sstables in higher levels that are "never" compacted.


--
This message was sent by Atlassian JIRA
(v6.2#6252)