-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated upgrade instructions #301
base: master
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -299,8 +299,6 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http://<dcos_url>/service/c | |
|
||
The command above will trigger the install of the new Cassandra version. You can follow the upgrade progress by making a REST request identical to the one used to follow the progress of a [configuration upgrade](/1.7/usage/service-guides/cassandra/configuration/). | ||
|
||
**Note:** The upgrade process will cause all of your Cassandra node processes to restart. | ||
|
||
**If you are upgrading to or beyond 1.0.13-X.Y.Z of DC/OS Apache Cassandra from an older version (pre `1.0.13-X.Y.Z`), here is the upgrade path:** | ||
|
||
1. Perform [Backup Operation](https://github.com/mesosphere/dcos-cassandra-service#backup) on your currently running Cassandra Service. Please make a note of the backup name and backup location. | ||
|
@@ -309,6 +307,11 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http://<dcos_url>/service/c | |
4. Once the restore operation is finished, check if the data is restored correctly. | ||
5. [Uninstall](https://github.com/mesosphere/dcos-cassandra-service#uninstall) old cluster. | ||
|
||
**Upgrade Notes:** | ||
* The upgrade process will cause all of your Cassandra node processes to restart. | ||
* Upgrades are supported from version `N` to `N + 1`. So, if you are on version `N` and want to get to version `N + 2`, please upgrade from version `N` to `N + 1` first, followed by an upgrade from `N + 1` to `N + 2`. | ||
* Upgrade from `1.0.15-3.0.7` to `1.0.16-3.0.8` is not supported. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bold pls. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Please upgrade from 15 to 17 directly"... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Currently, 1.0.15 to 1.0.15+ is unsupported. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can they still perform the backup/restore upgrade? Saying 'not supported' implies that's also not possible. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Or say that. I was just giving an example. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 |
||
|
||
# Uninstall | ||
|
||
Uninstalling a cluster is straightforward. Replace `cassandra` with the name of the Cassandra instance to be uninstalled. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be up at line 302. This is more important than the section on the special upgrade path.