Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 5 Mar 2015 00:34:38 +0000 (UTC)
From: "Takenori Sato (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12777766.1424920009000.4441.1425515678582@Atlassian.JIRA>
In-Reply-To: <JIRA.12777766.1424920009000@Atlassian.JIRA>
References: <JIRA.12777766.1424920009000@Atlassian.JIRA>
 <JIRA.12777766.1424920009785@arcas>
Subject: [jira] [Updated] (CASSANDRA-8866) PartitionedCompactionStrategy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Takenori Sato updated CASSANDRA-8866:
-------------------------------------
    Attachment: cassandra-2.0-8866.txt

confirmed it works as expected both on a single node and multi nodes env. Only two partitioners, Murmur3Partitioners and RandomPartitioners, are tested.

> PartitionedCompactionStrategy
> -----------------------------
>
>                 Key: CASSANDRA-8866
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8866
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Takenori Sato
>         Attachments: cassandra-2.0-8866.txt
>
>
> PartitionedCompactionStrategy is a new compaction strategy with the following goals in mind:
> * Column tombstone removal effectiveness
> * Read performance
> As the name suggests, PartitionedCompactionStrategy actively splits un-partitioned sstables(newly flushed, imported, compaction strategy switch) into partitions by IPartitioner. The number of nodes will be configurable.
> Then, PartitionedCompactionStrategy finds an interesting partition at compaction based on the followings:
> - the number of sstables
> - the ratio of droppable tombstones
> - read hotness
> You may think this design looks similar to SizeTieredCompactionStrategy and LeveledCompactionStrategy, but the big difference is that a compaction by PartitionedCompactionStrategy is based on rows(a partitions). And this allows more effective column tombstone removal, and better read performance.
> Also note that this will not require any changes to the other components. So this is expected to be a purely pluggable compaction strategy.
> A possible implementation of _PertitionedCompactionStrategy#getNextBackgroundTask()_ is as follows:
> # find un-partitioned sstables
> # split un-partitioned sstables into partitiones
> # group all the sstables into partitions
> # find an interesting partition
> #* the number of sstables
> #* the number of droppable tombstones
> #* hotness
> # create a compaction task for the interesting bucket if found


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