[
https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731600#comment-13731600
]
Jeremiah Jordan commented on CASSANDRA-5831:
--------------------------------------------
Something more needs to happen on migration for 1.2. Both sstableupgrade and
sstablescrub create a broken set of system tables.
{noformat}
ERROR 22:11:40,896 Fatal exception during initialization
org.apache.cassandra.exceptions.ConfigurationException: Found system table
files, but they couldn't be loaded!
at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:440)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:243)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:490)
{noformat}
Works fine if I just run ./cassandra to do the upgrade.
> 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-Handle-pre-1.1-data-directory-layout.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
