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 246D11817B for ; Tue, 10 Nov 2015 17:26:12 +0000 (UTC) Received: (qmail 5033 invoked by uid 500); 10 Nov 2015 17:26:11 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 4984 invoked by uid 500); 10 Nov 2015 17:26:11 -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 4475 invoked by uid 99); 10 Nov 2015 17:26:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2015 17:26:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 34AE12C1F58 for ; Tue, 10 Nov 2015 17:26:11 +0000 (UTC) Date: Tue, 10 Nov 2015 17:26:11 +0000 (UTC) From: "Marcus Eriksson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10422) Avoid anticompaction when doing subrange repair 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-10422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998954#comment-14998954 ] Marcus Eriksson commented on CASSANDRA-10422: --------------------------------------------- bq. do I even want to bother with preventing them from requesting subrange repair with incremental repair No, I think we can just skip anticompaction in this case. Maybe output a warning? bq. For 2.1 it's sufficient to prevent them from requesting the problem combination? yes > Avoid anticompaction when doing subrange repair > ----------------------------------------------- > > Key: CASSANDRA-10422 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10422 > Project: Cassandra > Issue Type: Bug > Reporter: Marcus Eriksson > Assignee: Ariel Weisberg > Fix For: 3.1, 2.1.x, 2.2.x > > > If we do split the owned range in say 1000 parts, and then do one repair each, we could potentially anticompact every sstable 1000 times (ie, we anticompact the repaired range out 1000 times). We should avoid anticompacting at all in these cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)