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 942B518834 for ; Thu, 29 Oct 2015 16:06:28 +0000 (UTC) Received: (qmail 51865 invoked by uid 500); 29 Oct 2015 16:06:28 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 51832 invoked by uid 500); 29 Oct 2015 16:06:28 -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 51552 invoked by uid 99); 29 Oct 2015 16:06:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2015 16:06:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 137FC2C1F56 for ; Thu, 29 Oct 2015 16:06:28 +0000 (UTC) Date: Thu, 29 Oct 2015 16:06:28 +0000 (UTC) From: "Ariel Weisberg (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=14980688#comment-14980688 ] Ariel Weisberg commented on CASSANDRA-10422: -------------------------------------------- [~krummas] Is this as simple as having a repair that has a start/end token(s) specified ignoring (or rejecting) the incremental repair flag? Say [here in RepairOption.parse|https://github.com/apache/cassandra/blob/ef1b4c0f5a8e0677efd3ec25fa735782ce1b1480/src/java/org/apache/cassandra/repair/messages/RepairOption.java#L143]? > 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: 2.1.x, 2.2.x, 3.1 > > > 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)