[jira] [Issue Comment Edited] (CASSANDRA-3989) nodetool cleanup/scrub/upgradesstables promotes all sstables to next level (LeveledCompaction)

["Maki Watanabe (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

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

Maki Watanabe edited comment on CASSANDRA-3989 at 3/7/12 2:48 AM:
------------------------------------------------------------------

Another problem with the fix.
In following condition, the background compaction task start looping.
- No L0 sstable
- Enough number of L1 sstables, exceed L1 capacity (compaction score > 1.1)

It seems the background task try to promote sstables to reduce compaction score, but it can't by this fix, then it will compact each L1 sstables forever.

                
      was (Author: makiw):
    Another problem with the fix.
In following condition, the background compaction task start looping.
- No L0 sstable
- Enough number of L1 sstables, exceed L1 capacity (compaction score > 1.1)
It seems the background task try to promote sstables to reduce compaction score, but it can't by this fix, then it will compact each L1 sstables forever.

                  
> nodetool cleanup/scrub/upgradesstables promotes all sstables to next level (LeveledCompaction)
> ----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3989
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3989
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: RHEL6
>            Reporter: Maki Watanabe
>            Assignee: Maki Watanabe
>            Priority: Minor
>             Fix For: 1.0.9, 1.1.0
>
>         Attachments: 0001-Fix-promote-not-to-promote-files-at-cleanup-compacti.patch
>
>
> 1.0.7 + LeveledCompactionStrategy
> If you run nodetool cleanup, scrub, or upgradesstables, Cassandra execute compaction for each sstable. During the compaction, it put the new sstable to next level of the original sstable. If you run cleanup many times, sstables will reached to the highest level, and CASSANDRA-3608 will happens at next cleanup.
> Reproduce procedure:
> # create column family CF1 with compaction_strategy=LeveledCompactionStrategy and compaction_strategy_options={sstable_size_in_mb: 5};
> # Insert some data into CF1.
> # nodetool flush
> # Verify the sstable is created at L1 in CF1.json
> # nodetool cleanup
> # Verify sstable in L1 is removed and new sstable is created at L2 in CF1.json
> # repeat nodetool cleanup some times

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira