You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/11/09 01:02:17 UTC

[jira] [Updated] (CASSANDRA-6323) Create new sstables in the highest possible level

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

Jonathan Ellis updated CASSANDRA-6323:
--------------------------------------

    Reviewer:   (was: Marcus Eriksson)
    Assignee:     (was: Jonathan Ellis)

Ugh, I thought it would be simple to bust this out, but the critical difference is that leveldb has single-threaded compaction.  For us we'd need to keep track of currently-being-written (compacted or flushed) sstables to check for overlaps as well.

> Create new sstables in the highest possible level
> -------------------------------------------------
>
>                 Key: CASSANDRA-6323
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6323
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>              Labels: compaction
>             Fix For: 2.0.3
>
>
> See PickLevelForMemTableOutput here: https://code.google.com/p/leveldb/source/browse/db/version_set.cc#507
> (Moving from CASSANDRA-5936)



--
This message was sent by Atlassian JIRA
(v6.1#6144)