[
https://issues.apache.org/jira/browse/CASSANDRA-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maki Watanabe updated CASSANDRA-3989:
-------------------------------------
Attachment: 0001-Fix-promote-not-to-promote-files-at-cleanup-compacti.patch
Fix LeveledManifest.promote will not promote sstables to next level if the
number of source sstables (removed) is one.
> 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.7
> Environment: RHEL6
> Reporter: Maki Watanabe
> Priority: Minor
> 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
