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 7F1D318C55 for ; Thu, 14 Jan 2016 14:46:40 +0000 (UTC) Received: (qmail 39142 invoked by uid 500); 14 Jan 2016 14:46:40 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 39093 invoked by uid 500); 14 Jan 2016 14:46:40 -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 38868 invoked by uid 99); 14 Jan 2016 14:46:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jan 2016 14:46:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 077052C03DA for ; Thu, 14 Jan 2016 14:46:40 +0000 (UTC) Date: Thu, 14 Jan 2016 14:46:40 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10847) Log a message when refusing a major compaction due to incremental repairedAt status 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-10847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098193#comment-15098193 ] Sylvain Lebresne commented on CASSANDRA-10847: ---------------------------------------------- bq. I wanted to have the same message in 3.2+ where we major compact to 2 files per data directory Hum, we might want some tweaking for that I suppose, but the previous message would have given you the wrong reason for that case in some case anyway :) > Log a message when refusing a major compaction due to incremental repairedAt status > ----------------------------------------------------------------------------------- > > Key: CASSANDRA-10847 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10847 > Project: Cassandra > Issue Type: Improvement > Components: Compaction > Reporter: Brandon Williams > Assignee: Marcus Eriksson > Priority: Trivial > Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x > > > When you do a major compaction, but have some repaired sstables and some that are not, it will correctly not compact them together. However, it can be somewhat confusing the operator as to *why* they aren't compacting together. It would be beneficial, specifically when doing a major, to log that we aren't going to do a full major because of this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)