Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D8AF0109FC for ; Tue, 11 Feb 2014 15:43:45 +0000 (UTC) Received: (qmail 3929 invoked by uid 500); 11 Feb 2014 15:43:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 3766 invoked by uid 500); 11 Feb 2014 15:43:24 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 3750 invoked by uid 99); 11 Feb 2014 15:43:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 15:43:22 +0000 Date: Tue, 11 Feb 2014 15:43:22 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6688) Avoid possible sstable overlaps with leveled compaction MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897933#comment-13897933 ] Jonathan Ellis commented on CASSANDRA-6688: ------------------------------------------- bq. Second case is where we try to include as many overlapping L0 sstables as possible, here we could add sstables that are not compacting, but overlap sstables that are. This affects 1.2 as well right? > Avoid possible sstable overlaps with leveled compaction > ------------------------------------------------------- > > Key: CASSANDRA-6688 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6688 > Project: Cassandra > Issue Type: Bug > Reporter: Marcus Eriksson > Assignee: Marcus Eriksson > Attachments: 0001-6688.patch > > > Two cases where we can end up with overlapping sstables in the leveled manifest; > FIrst one is when we skip levels during compaction. Here we need to make sure we are not compacting in newLevel - 1 since if, for example, we are doing a L1 -> L2 compaction and then start a new L0 compaction where we decide to skip L1, we could have overlapping sstables in L2 when the compactions are done. This case is new in 2.0 since we check if we skip levels before the compaction starts. > Second case is where we try to include as many overlapping L0 sstables as possible, here we could add sstables that are not compacting, but overlap sstables that are. -- This message was sent by Atlassian JIRA (v6.1.5#6160)