[jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
[
https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-5831:
---
Attachment: 0002-Handle-old-system-data-in-health-check.patch
Patch 0002 alters the failing health check to also look for a saved cluster
name in {{System.LocationInfo}}, which indicates that the system data has not
been migrated yet (it happens at the end of the startup process, whereas the
health check is early in the startup process).
I also have a [branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-5831]
that contains the two patches.
> 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,
> 0002-Handle-old-system-data-in-health-check.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
[jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
[ https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5831: -- Reviewer: jjordan > 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
[jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
[
https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-5831:
---
Attachment: 0001-Handle-pre-1.1-data-directory-layout.patch
The new 0001 patch adds a {{\-\-migrate}} option to {{sstableupgrade}} and
{{sstablescrub}}. If that option is not used and a pre-1.1 layout is detected,
both tools will error out and mention the {{\-\-migrate}} option. If the
option is used, all keyspaces and column families will be migrated.
> 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
[jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
[ https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-5831: --- Attachment: (was: 0001-Check-for-current-directory-layout-before-upgrading.patch) > 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 > > > 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
[jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
[ 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
[jira] [Updated] (CASSANDRA-5831) Running sstableupgrade on C* 1.0 data dir, before starting C* 1.2 for the first time breaks stuff
[ https://issues.apache.org/jira/browse/CASSANDRA-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5831: -- Component/s: Tools Priority: Minor (was: Major) Fix Version/s: 1.2.9 Assignee: Tyler Hobbs I think all we need to do here is "don't run upgradesstables if the ks/cf/ heirarchy doesn't exist already for the system tables." In particular, upgradesstables against a 1.1 install should be fine. > 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 > > > 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
