You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Constance Eustace (JIRA)" <ji...@apache.org> on 2015/11/17 00:07:11 UTC

[jira] [Updated] (CASSANDRA-10716) nodetool cleanup - row key subrange cleanup like repair -st and -et

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

Constance Eustace updated CASSANDRA-10716:
------------------------------------------
    Summary: nodetool cleanup - row key subrange cleanup like repair -st and -et  (was: cleanup - row key range like repair)

> nodetool cleanup - row key subrange cleanup like repair -st and -et
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-10716
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10716
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Constance Eustace
>            Priority: Minor
>
> Although the need probably isn't the same as reducing the Merkle tree size/scope streaming problem, it would be nice to do subrange cleans so we can gauge statistical samples of disk space savings, or split it into many subtasks so we can track progress, or gradually perform it over time to reduce I/O impacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)