cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7409) Allow multiple overlapping sstables in L1
Date Tue, 29 Jul 2014 09:19:38 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077543#comment-14077543
] 

Marcus Eriksson commented on CASSANDRA-7409:
--------------------------------------------

We should probably make this behave as standard LCS when MAX_OVERLAPPING_LEVEL_OPTION is 0
and not have a separate compaction strategy

Benchmarks will be very interesting

> Allow multiple overlapping sstables in L1
> -----------------------------------------
>
>                 Key: CASSANDRA-7409
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7409
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Carl Yeksigian
>            Assignee: Carl Yeksigian
>
> Currently, when a normal L0 compaction takes place (not STCS), we take up to MAX_COMPACTING_L0
L0 sstables and all of the overlapping L1 sstables and compact them together. If we didn't
have to deal with the overlapping L1 tables, we could compact a higher number of L0 sstables
together into a set of non-overlapping L1 sstables.
> This could be done by delaying the invariant that L1 has no overlapping sstables. Going
from L1 to L2, we would be compacting fewer sstables together which overlap.
> When reading, we will not have the same one sstable per level (except L0) guarantee,
but this can be bounded (once we have too many sets of sstables, either compact them back
into the same level, or compact them up to the next level).
> This could be generalized to allow any level to be the maximum for this overlapping strategy.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message