Skip to content

Commit 32ebd46

Browse files
authored
[DOCS] Add deprecation docs for cluster recovery defer settings (#77786) (#77956)
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.
1 parent 3de74ec commit 32ebd46

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/reference/migration/migrate_7_7.asciidoc

+19
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,25 @@ If you configure more than one realm of any type with the same order, the node w
9797
The `auth.password` setting for the monitoring HTTP exporter has been deprecated and will be
9898
removed in version 8.0.0. Please use the `auth.secure_password` setting instead.
9999

100+
[discrete]
101+
[[deprecate-defer-cluster-recovery-settings]]
102+
==== Settings used to defer cluster recovery pending a certain number of master nodes are deprecated.
103+
104+
The following cluster settings are now deprecated:
105+
106+
* `gateway.expected_nodes`
107+
* `gateway.expected_master_nodes`
108+
* `gateway.recover_after_nodes`
109+
* `gateway.recover_after_master_nodes`
110+
111+
It is safe to recover the cluster as soon as a majority of master-eligible nodes
112+
have joined. There is no benefit in waiting for any additional master-eligible
113+
nodes to start.
114+
115+
To avoid deprecation warnings, discontinue use of the deprecated settings. If
116+
needed, use `gateway.expected_data_nodes` or `gateway.recover_after_data_nodes`
117+
to defer cluster recovery pending a certain number of data nodes.
118+
100119
[discrete]
101120
[[breaking_77_search_changes]]
102121
=== Search changes

0 commit comments

Comments
 (0)