[ https://issues.apache.org/jira/browse/CASSANDRA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612721#comment-13612721 ]
Rafal Kwasny commented on CASSANDRA-5366: ----------------------------------------- Any chances this will get into 1.1.4? we have exactly the same problem, after upgrading to 1.2 we need to run upgradesstables and with 1TB data/node doing it twice for some sstables is a waste of time. > UpgradeSSTables Optimisation > ---------------------------- > > Key: CASSANDRA-5366 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5366 > Project: Cassandra > Issue Type: Improvement > Reporter: Brooke Bryan > Assignee: Sylvain Lebresne > Fix For: 1.2.4 > > Attachments: 5366.txt > > > 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