You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lyuben Todorov (JIRA)" <ji...@apache.org> on 2013/08/19 16:09:48 UTC

[jira] [Updated] (CASSANDRA-5891) Scrub disk footprint needs to be reduced

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

Lyuben Todorov updated CASSANDRA-5891:
--------------------------------------

    Attachment: 5891.patch

Added a -no-snapshot parameter to the "nodetool scrub" command. When supplied, the parameter tells scrub to skip snapshot creation and saves disk space:

The below is for the size of the var/lib/cassandra directory
./nodetool scrub with -no-snapshot: cassandra dir size before scrub: 4.1G, after scrub 4.1G
./nodetool scrub (without -no-snapshot): cassandra dir size before scrub: 4.1G, after scrub 7.1G
                
> Scrub disk footprint needs to be reduced
> ----------------------------------------
>
>                 Key: CASSANDRA-5891
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5891
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: Lyuben Todorov
>            Priority: Minor
>         Attachments: 5891.patch
>
>
> Currently scrub creates a snapshot at the beginning of the scrub. This causes the disk used to be doubled after the scrub. 
> If the disk utilization is more than 50%, scrub wont work. It would be nice to have an overriding option to disable snapshot. Something like --no-snapshot.

--
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