Skip to content

[DOCS] Use transient setting to reenabled allocation. Closes #27677 #28757

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

Closed
wants to merge 1 commit into from
Closed

[DOCS] Use transient setting to reenabled allocation. Closes #27677 #28757

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 7 additions & 1 deletion docs/reference/upgrade/cluster_restart.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,13 +94,19 @@ reenable allocation.
------------------------------------------------------
PUT _cluster/settings
{
"persistent": {
"transient": {
"cluster.routing.allocation.enable": "all"
}
}
------------------------------------------------------
// CONSOLE

NOTE: Because <<cluster-update-settings.html#_precedence_of_settings, transient
settings take precedence over persistent settings>>, this overrides the
persistent setting used to disable shard allocation in the first step. If you
don't explicitly reenable shard allocation after a full cluster restart, the
persistent setting is used and shard allocation remains disabled.

Once allocation is reenabled, the cluster starts allocating replica shards to
the data nodes. At this point it is safe to resume indexing and searching,
but your cluster will recover more quickly if you can wait until all primary
Expand Down
8 changes: 7 additions & 1 deletion docs/reference/upgrade/rolling_upgrade.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,12 @@ GET _cat/nodes
+
--

NOTE: Because <<cluster-update-settings.html#_precedence_of_settings, transient
settings take precedence over persistent settings>>, this overrides the
persistent setting used to disable shard allocation in the first step. If you
don't explicitly reenable shard allocation after a full cluster restart, the
persistent setting is used and shard allocation remains disabled.

Once the node has joined the cluster, reenable shard allocation to start using
the node:

Expand Down Expand Up @@ -156,4 +162,4 @@ In the unlikely case of a network malfunction during the upgrade process that
isolates all remaining old nodes from the cluster, you must take the
old nodes offline and upgrade them to enable them to join the cluster.

====================================================
====================================================