Skip to content

[DOCS] Remove upgrade step that stops machine learning #219

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

Merged
merged 4 commits into from
Feb 19, 2019
Merged

[DOCS] Remove upgrade step that stops machine learning #219

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b25381e
[DOCS] Remove step for stopping ML
lcawl Feb 14, 2019
a9d3253
Merge remote-tracking branch 'upstream/master' into ml-upgrade
lcawl Feb 19, 2019
582d7a4
[DOCS] Re-add ML warning
lcawl Feb 19, 2019
2a05944
[DOCS] Final edit
lcawl Feb 19, 2019
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
4 changes: 0 additions & 4 deletions docs/upgrading-stack.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,10 +68,6 @@ restart all nodes to maintain communication across the cluster.
password (`changeme`). For more information, see
{stack-ov}/built-in-users.html[Built-in users].

. Stop any {ml} jobs that are running before starting the
upgrade process. See
{stack-ov}/stopping-ml.html[Stopping {ml}].
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe instead of completely removing this section it could say something like "Consider stopping any {ml} jobs that are running - see <close_ml.asciidoc> for the pros and cons of doing this".

Or do you think that's just too complicated for this guide?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, I've altered that text.


IMPORTANT: Test upgrades in a dev environment before upgrading your
production cluster.

Expand Down