From 3401223452c14fb38194c85e6b1ac5f20397a322 Mon Sep 17 00:00:00 2001 From: Mohit Soni Date: Mon, 31 Oct 2016 17:09:46 -0700 Subject: [PATCH 1/3] Updated upgrade instructions --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7d39d2f1..e4e2e1bb 100644 --- a/README.md +++ b/README.md @@ -299,8 +299,6 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http:///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:///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. + # Uninstall Uninstalling a cluster is straightforward. Replace `cassandra` with the name of the Cassandra instance to be uninstalled. From ed2f9953a0944d3cc5f86f565202a2667f88b702 Mon Sep 17 00:00:00 2001 From: Mohit Soni Date: Mon, 31 Oct 2016 21:59:52 -0700 Subject: [PATCH 2/3] Improved upgrade instructions --- README.md | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index e4e2e1bb..afcb8140 100644 --- a/README.md +++ b/README.md @@ -292,6 +292,21 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http:///service/c # Upgrade +## Overview + +* Framework version has two components: `A.B.C-X.Y.Z`, where `A.B.C` is the scheduler version and `X.Y.Z` is the version of supported Apache Cassandra. +* Upgrade process will cause a rolling restart of all Cassandra Node processes in the cluster. +* Upgrades are supported from version `N` to `N + 1`. For ex: Upgrade from `1.0.16-3.0.8` is `1.0.17-3.0.8` is supported. +* In order to upgrade from version `N` to `N + 2`, please upgrade from version `N` to `N + 1` first, followed by an upgrade from `N + 1` to `N + 2`. + +| Version N | Version N + 1 | Method | +| ------------- |:-------------:| -------------:| +| 1.0.15-3.0.7 | 1.0.16-3.0.8 | Side-by-Side | +| 1.0.16-3.0.8 | 1.0.17-3.0.8 | In-place | + + +## Instructions - In-place upgrades + 1. In the DC/OS web interface, destroy the Cassandra instance to be updated. (This will not kill Cassandra node tasks). 1. Verify that you no longer see the Cassandra instance in the DC/OS web interface. 1. From the DC/OS CLI, install the latest version of Cassandra [with any customizations you require](1.7/usage/service-guides/cassandra/install-and-customize/) in a JSON options file: @@ -299,7 +314,7 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http:///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/). -**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:** +## Instructions - Side-by-side upgrade 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. 2. [Install a new Cassandra Service](https://github.com/mesosphere/dcos-cassandra-service#multiple-cassandra-cluster-installation) instance. @@ -307,11 +322,6 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http:///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. - # Uninstall Uninstalling a cluster is straightforward. Replace `cassandra` with the name of the Cassandra instance to be uninstalled. From 3d424433523cd14fc423b4e5613bb291990c4643 Mon Sep 17 00:00:00 2001 From: Mohit Soni Date: Mon, 31 Oct 2016 22:07:11 -0700 Subject: [PATCH 3/3] Update README.md --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index afcb8140..6bcdfb16 100644 --- a/README.md +++ b/README.md @@ -301,6 +301,9 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http:///service/c | Version N | Version N + 1 | Method | | ------------- |:-------------:| -------------:| +| 1.0.12-2.2.5 | 1.0.13-2.2.5 | Side-by-Side | +| 1.0.13-2.2.5 | 1.0.14-2.2.5 | In-place | +| 1.0.14-3.0.7 | 1.0.15-3.0.8 | In-place | | 1.0.15-3.0.7 | 1.0.16-3.0.8 | Side-by-Side | | 1.0.16-3.0.8 | 1.0.17-3.0.8 | In-place |