You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vitalii Tymchyshyn (JIRA)" <ji...@apache.org> on 2012/09/07 11:25:07 UTC

[jira] [Commented] (CASSANDRA-4467) insufficient space for compaction when upgrade compaction strategy from SizeTiered to Leveled

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

Vitalii Tymchyshyn commented on CASSANDRA-4467:
-----------------------------------------------

I did also hit this. Upgrade requires double the space. As for me, workaround was to move large files out of data directory, upgrade, then move them back to be picked up.
I'd say LeveledCompaction upgrade can do the same - convert not all at once, but as much as it can multiple times. It will be slower, but you won't have this:

 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,600 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,600 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,600 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,601 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,601 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,601 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,601 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,602 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,602 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,602 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,602 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,602 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,603 CompactionTask.java (line 94) insufficient space to compact; aborting compaction
 WARN [CompactionExecutor:17] 2012-09-07 12:09:47,603 CompactionTask.java (line 94) insufficient space to compact; aborting compaction

BTW: When I did return files and asked to discover new files, It've also picked up some files current compaction run was producing. Dunno if it's OK.
                
> insufficient space for compaction when upgrade compaction strategy from SizeTiered to Leveled
> ---------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4467
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4467
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: Ubuntu,Oracle Java 1.7,Cassandra 1.0.10
>            Reporter: Cheng Zhang
>            Assignee: Yuki Morishita
>            Priority: Minor
>
> Cassandra has two data directories as follow:
> cassandra-disk0 use about 500G, about 250G free space
> cassandra-disk1 use about 500G, about 250G free space
> The max data file is about 400G. When I upgrade from SizeTieredCompactionStrategy to LeveledCompactionStrategy, there is no space to do this, for the free space of every data directory is small than the largest data file. But the total free space is enough for compaction.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira