Skip to content

Commit

Permalink
[DOCS] Add deprecation docs for cluster recovery defer settings (#77786
Browse files Browse the repository at this point in the history
…) (#77959)

We deprecated the following settings in 7.7 with PR #53646:

* `gateway.expected_nodes`
* `gateway.expected_master_nodes`
* `gateway.recover_after_nodes`
* `gateway.recover_after_master_nodes`

However, we didn't add a related item to the 7.7 deprecation docs. This adds the
missing item.

Relates to #53845.
  • Loading branch information
jrodewig authored Sep 16, 2021
1 parent 8d7060d commit 0c2cd97
Showing 1 changed file with 19 additions and 0 deletions.
19 changes: 19 additions & 0 deletions docs/reference/migration/migrate_7_7.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,25 @@ If you configure more than one realm of any type with the same order, the node w
The `auth.password` setting for the monitoring HTTP exporter has been deprecated and will be
removed in version 8.0.0. Please use the `auth.secure_password` setting instead.

[discrete]
[[deprecate-defer-cluster-recovery-settings]]
==== Settings used to defer cluster recovery pending a certain number of master nodes are deprecated.

The following cluster settings are now deprecated:

* `gateway.expected_nodes`
* `gateway.expected_master_nodes`
* `gateway.recover_after_nodes`
* `gateway.recover_after_master_nodes`

It is safe to recover the cluster as soon as a majority of master-eligible nodes
have joined. There is no benefit in waiting for any additional master-eligible
nodes to start.

To avoid deprecation warnings, discontinue use of the deprecated settings. If
needed, use `gateway.expected_data_nodes` or `gateway.recover_after_data_nodes`
to defer cluster recovery pending a certain number of data nodes.

[discrete]
[[breaking_77_search_changes]]
=== Search changes
Expand Down

0 comments on commit 0c2cd97

Please sign in to comment.