Skip to content
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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Updated upgrade instructions #301

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3401223
Updated upgrade instructions
mohitsoni Nov 1, 2016
ed2f995
Improved upgrade instructions
mohitsoni Nov 1, 2016
3d42443
Update README.md
mohitsoni Nov 1, 2016
ebd492d
Merge branch 'master' into upgrade-notice
nickbp Nov 2, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 19 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -296,16 +296,32 @@ $ curl -X POST -H "Authorization: token=$AUTH_TOKEN" http://<dcos_url>/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.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 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't it be 1.0.15-3.0.7 here?

| 1.0.15-3.0.7 | 1.0.16-3.0.8 | Side-by-Side |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't side-by-side unavailable due to the backup regression on 1.0.15?

| 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:
$ dcos package install cassandra --options=/path/to/options.json

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:**
## Instructions - Side-by-side upgrade

1. Perform [Backup Operation](https://github.com/mesosphere/dcos-cassandra-service#backup) on your currently running Cassandra Service. Note the backup name and backup location.
1. [Install a new Cassandra Service](https://github.com/mesosphere/dcos-cassandra-service#multiple-cassandra-cluster-installation) instance.
Expand Down