[
https://issues.apache.org/jira/browse/CASSANDRA-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lerh Chuan Low updated CASSANDRA-10540:
---------------------------------------
Description:
{color:red}colored text{color}Broken out from CASSANDRA-6696, we should split
sstables based on ranges during compaction.
Requirements;
* dont create tiny sstables - keep them bunched together until a single vnode
is big enough (configurable how big that is)
* make it possible to run existing compaction strategies on the per-range
sstables
We should probably add a global compaction strategy parameter that states
whether this should be enabled or not.
was:
Broken out from CASSANDRA-6696, we should split sstables based on ranges during
compaction.
Requirements;
* dont create tiny sstables - keep them bunched together until a single vnode
is big enough (configurable how big that is)
* make it possible to run existing compaction strategies on the per-range
sstables
We should probably add a global compaction strategy parameter that states
whether this should be enabled or not.
> RangeAwareCompaction
> --------------------
>
> Key: CASSANDRA-10540
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10540
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Major
> Labels: compaction, lcs, vnodes
> Fix For: 4.x
>
>
> {color:red}colored text{color}Broken out from CASSANDRA-6696, we should split
> sstables based on ranges during compaction.
> Requirements;
> * dont create tiny sstables - keep them bunched together until a single vnode
> is big enough (configurable how big that is)
> * make it possible to run existing compaction strategies on the per-range
> sstables
> We should probably add a global compaction strategy parameter that states
> whether this should be enabled or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]