Skip to content

[DOCS] Adds test clause to the code snippets in the cluster restart page #49023

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 2 commits into from
Nov 13, 2019
Merged

[DOCS] Adds test clause to the code snippets in the cluster restart page #49023

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
890d6aa
[DOCS] Adds test clause to the code snippets in the cluster restart p…
szabosteve Nov 13, 2019
2b5a049
[DOCS] Changes test comment.
szabosteve Nov 13, 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
7 changes: 7 additions & 0 deletions docs/reference/setup/restart-cluster.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,7 @@ prevent new jobs from opening by using the
--------------------------------------------------
POST _ml/set_upgrade_mode?enabled=true
--------------------------------------------------
// TEST
+
When you disable upgrade mode, the jobs resume using the last model state that
was automatically saved. This option avoids the overhead of managing active jobs
Expand Down Expand Up @@ -88,6 +89,7 @@ GET _cat/health

GET _cat/nodes
--------------------------------------------------
// TEST[continued]

The `status` column returned by `_cat/health` shows the health of each node
in the cluster: `red`, `yellow`, or `green`.
Expand Down Expand Up @@ -124,6 +126,7 @@ PUT _cluster/settings
}
}
------------------------------------------------------
// TEST[continued]

Once allocation is re-enabled, the cluster starts allocating replica shards to
the data nodes. At this point it is safe to resume indexing and searching,
Expand All @@ -140,6 +143,7 @@ GET _cat/health

GET _cat/recovery
--------------------------------------------------
// TEST[continued]
--
// tag::restart_ml[]
. *Restart machine learning jobs.* (Optional)
Expand All @@ -152,6 +156,7 @@ If you temporarily halted the tasks associated with your {ml} jobs, use the
--------------------------------------------------
POST _ml/set_upgrade_mode?enabled=false
--------------------------------------------------
// TEST[continued]

If you closed all {ml} jobs before stopping the nodes, open the jobs and start
the datafeeds from {kib} or with the <<ml-open-job,open jobs>> and
Expand Down Expand Up @@ -197,6 +202,7 @@ by submitting a `_cat/nodes` request:
--------------------------------------------------
GET _cat/nodes
--------------------------------------------------
// TEST[continued]
--

. *Reenable shard allocation.*
Expand All @@ -215,6 +221,7 @@ PUT _cluster/settings
}
}
--------------------------------------------------
// TEST[continued]
--

. *Repeat in case of rolling restart.*
Expand Down