cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
Date Wed, 31 Jul 2013 20:47:48 GMT

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

Tyler Hobbs updated CASSANDRA-5831:
-----------------------------------

    Attachment: 0001-Check-for-current-directory-layout-before-upgrading.patch

Attached patch 0001 does exactly that.
                
> Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time
breaks stuff
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5831
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5831
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Jeremiah Jordan
>            Assignee: Tyler Hobbs
>            Priority: Minor
>             Fix For: 1.2.9
>
>         Attachments: 0001-Check-for-current-directory-layout-before-upgrading.patch
>
>
> If you try to upgrade from C* 1.0.X to 1.2.X and run offline sstableupgrade to try and
migrate the sstables before starting 1.2.X for the first time, it messes up the system folder,
because it doesn't migrate it right, and then C* 1.2 can't start.
> sstableupgrade should either refuse to run against a C* 1.0 data folder, or migrate stuff
the right way.

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