[
https://issues.apache.org/jira/browse/CASSANDRA-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-4556.
---------------------------------------
Resolution: Later
As you point out, there are a number of reasonable workarounds. Doesn't look
like it's worth writing a ton of special case code for switching from strategy
X to strategy Y, but if you want to submit a patch I'll be happy to review it.
> upgrade from SizeTiered to Leveled failed because no enough free space
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-4556
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4556
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Affects Versions: 1.0.10
> Environment: Cassandra 1.0.10, Ubuntu 64bit server.
> Reporter: Cheng Zhang
>
> I use cassandra 1.0.10 with two data directories and
> SizeTieredCompactionStrategy first, after some time, the total free space is
> smaller than the biggest data file. At this time, I want change the
> compaction strategy to Leveled to save more space. But failed because there
> is no enough space for the biggest data file to compact.
> But when I change some code, if the biggest data file can't compact, I choose
> the second biggest data file to compact, the rest can be done in the same
> manner.The biggest data file will be compact when there is enough space. As
> the compaction goes by, there will be enough space.
--
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