[
https://issues.apache.org/jira/browse/CASSANDRA-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445273#comment-16445273
]
Marcus Eriksson edited comment on CASSANDRA-10540 at 4/20/18 4:21 AM:
----------------------------------------------------------------------
[~Lerh Low] yeah its still on my plate, just not very happy with it at the
moment, mostly because of the number of compaction strategy instances it runs
with vnodes (#tokens * rf * (2 + #pending repairs)), might need to group vnodes
to get it down to a reasonable number or something.
was (Author: krummas):
[~Lerh Low] yeah its still on my plate, just not very happy with it at the
moment, mostly because of the number of compaction strategy instances it runs
with vnodes (#tokens * rf), might need to group vnodes to get it down to a
reasonable number or something.
> 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
>
>
> 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]
