Updated upgrade instructions #301
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
triclambert
suggested changes
Nov 1, 2016
| **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.
"Please upgrade from 15 to 17 directly"...
There was a problem hiding this comment.
Currently, 1.0.15 to 1.0.15+ is unsupported.
There was a problem hiding this comment.
Can they still perform the backup/restore upgrade? Saying 'not supported' implies that's also not possible.
There was a problem hiding this comment.
Or say that. I was just giving an example.
| @@ -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:** | |||
There was a problem hiding this comment.
I think this should be up at line 302. This is more important than the section on the special upgrade path.
|
Ready to merge? |
nickbp
reviewed
Nov 2, 2016
| | 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 | |
There was a problem hiding this comment.
isn't side-by-side unavailable due to the backup regression on 1.0.15?
nickbp
reviewed
Nov 2, 2016
| | ------------- |:-------------:| -------------:| | ||
| | 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 | |
There was a problem hiding this comment.
shouldn't it be 1.0.15-3.0.7 here?
triclambert
approved these changes
Nov 16, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.