Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 2 Dec 2015 09:31:11 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12862261.1441642781000.243254.1449048671418@Atlassian.JIRA>
In-Reply-To: <JIRA.12862261.1441642781000@Atlassian.JIRA>
References: <JIRA.12862261.1441642781000@Atlassian.JIRA>
 <JIRA.12862261.1441642781459@arcas>
Subject: [jira] [Updated] (CASSANDRA-10280) Make DTCS work well with old
 data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-10280:
----------------------------------------
    Component/s: Compaction

> Make DTCS work well with old data
> ---------------------------------
>
>                 Key: CASSANDRA-10280
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10280
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Compaction
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>              Labels: docs-impacting, dtcs
>             Fix For: 2.1.12, 2.2.4, 3.0.1, 3.1
>
>
> Operational tasks become incredibly expensive if you keep around a long timespan of data with DTCS - with default settings and 1 year of data, the oldest window covers about 180 days. Bootstrapping a node with vnodes with this data layout will force cassandra to compact very many sstables in this window.
> We should probably put a cap on how big the biggest windows can get. We could probably default this to something sane based on max_sstable_age (ie, say we can reasonably handle 1000 sstables per node, then we can calculate how big the windows should be to allow that)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)