cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5366) UpgradeSSTables Optimisation
Date Wed, 20 Mar 2013 18:35:15 GMT

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

Jonathan Ellis commented on CASSANDRA-5366:
-------------------------------------------

Can we just use scrub for that?  It's a bit heavier-weight but it's not a super common scenario.
                
> UpgradeSSTables Optimisation
> ----------------------------
>
>                 Key: CASSANDRA-5366
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5366
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brooke Bryan
>
> Currently, if you run upgradesstables, cassandra will run through every single SSTable
within the scope of the request.  Where we have some large tables, an upgrade on a single
sstable can take hours, even if its already sat on the same version.
> After upgrading to a new cassandra version, it would be ideal to be able to upgrade only
sstables not sat in the latest version, as it seems like it just needs to do a massive amount
of disk IO, with nothing being achieved at the end of it.
> Maybe its worth putting an option onto the nodetool command, or creating a new command
for this type of upgrade

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

Mime
View raw message