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 A26DF18066 for ; Tue, 13 Oct 2015 21:32:06 +0000 (UTC) Received: (qmail 96267 invoked by uid 500); 13 Oct 2015 21:32:06 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 96233 invoked by uid 500); 13 Oct 2015 21:32:06 -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 96216 invoked by uid 99); 13 Oct 2015 21:32:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2015 21:32:06 +0000 Date: Tue, 13 Oct 2015 21:32:06 +0000 (UTC) From: "Alan Boudreault (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-10490) DTCS historic compaction, possibly with major 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-10490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Boudreault updated CASSANDRA-10490: ---------------------------------------- Labels: compaction triage (was: compaction) > DTCS historic compaction, possibly with major compaction > -------------------------------------------------------- > > Key: CASSANDRA-10490 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10490 > Project: Cassandra > Issue Type: Improvement > Reporter: Jonathan Shook > Labels: compaction, triage > Fix For: 3.x, 2.2.x > > > Presently, it's simply painful to run a major compaction with DTCS. It doesn't really serve a useful purpose. Instead, a DTCS major compaction should allow for a DTCS-style compaction to go back before max_sstable_age_days. We can call this a historic compaction, for lack of a better term. > Such a compaction should not take precedence over normal compaction work, but should be considered a background task. By default there should be a cap on the number of these tasks running. It would be nice to have a separate "max_historic_compaction_tasks" and possibly a "max_historic_compaction_throughput" in the compaction settings to allow for separate throttles on this. I would set these at 1 and 20% of the usual compaction throughput if they aren't set explicitly. > It may also be desirable to allow historic compaction to run apart from running a major compaction, and to simply disable major compaction altogether for DTCS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)