@@ -115,6 +115,11 @@ the resources available to handle the extra load that will result.
115115
116116NOTE: {cloud-only}
117117
118+ WARNING: This feature is available in {es} 7.17.1 and 8.0.1 onwards but is not
119+ supported in {es} 8.0.0. As such the recovery settings for managed services should
120+ be removed before upgrading to 8.0.0. It is possible to configure the settings in
121+ 7.17.1 and then upgrade to 8.0.1 directly.
122+
118123When running {es} as a managed service, the following settings allow the
119124service to specify absolute maximum bandwidths for disk reads, disk writes, and
120125network traffic on each node, and permit you to control the maximum recovery
@@ -136,10 +141,8 @@ writes, and network transfers using `node.bandwidth.recovery.disk.read`,
136141`node.bandwidth.recovery.disk.write` and `node.bandwidth.recovery.network`
137142respectively, and you can set the proportion of the absolute maximum bandwidth
138143that may be used for recoveries by adjusting
139- `node.bandwidth.recovery.factor.read` and
140- `node.bandwidth.recovery.factor.write`. If the {operator-feature} is enabled
141- then the service may also set default proportions using operator-only variants
142- of these settings.
144+ `node.bandwidth.recovery.operator.factor.read` and
145+ `node.bandwidth.recovery.operator.factor.write`.
143146
144147If you set `indices.recovery.max_bytes_per_sec` then {es} will use its value
145148for the maximum recovery bandwidth, as long as this does not exceed the
@@ -172,51 +175,27 @@ for a recovery-like workload on the node, which applies to both reads and
172175writes. If set, `node.bandwidth.recovery.disk.read` and
173176`node.bandwidth.recovery.disk.write` must also be set.
174177
175- `node.bandwidth.recovery.factor.read`::
176- (float, <<dynamic-cluster-setting,dynamic>>) The proportion of the maximum read
177- bandwidth that may be used for recoveries if
178- `indices.recovery.max_bytes_per_sec` is not set. Must be greater than `0` and
179- not greater than `1`. If not set, the value of
180- `node.bandwidth.recovery.operator.factor.read` is used. If no factor settings
181- are set then the value `0.4` is used.
182-
183- `node.bandwidth.recovery.factor.write`::
184- (float, <<dynamic-cluster-setting,dynamic>>) The proportion of the maximum
185- write bandwidth that may be used for recoveries if
186- `indices.recovery.max_bytes_per_sec` is not set. Must be greater than `0` and
187- not greater than `1`. If not set, the value of
188- `node.bandwidth.recovery.operator.factor.write` is used. If no factor settings
189- are set then the value `0.4` is used.
190-
191178`node.bandwidth.recovery.operator.factor.read`::
192- (float, <<dynamic-cluster-setting,dynamic>>) The proportion of the maximum read
193- bandwidth that may be used for recoveries if
194- `indices.recovery.max_bytes_per_sec` and `node.bandwidth.recovery.factor.read`
195- are not set. Must be greater than `0` and not greater than `1`. If not set, the
179+ (float) The proportion of the maximum read
180+ bandwidth that may be used for recoveries if `indices.recovery.max_bytes_per_sec`
181+ is not set. Must be greater than `0` and not greater than `1`. If not set, the
196182value of `node.bandwidth.recovery.operator.factor` is used. If no factor
197- settings are set then the value `0.4` is used. When the {operator-feature} is
198- enabled, this setting can be updated only by operator users.
183+ settings are set then the value `0.4` is used.
199184
200185`node.bandwidth.recovery.operator.factor.write`::
201- (float, <<dynamic-cluster-setting,dynamic>>) The proportion of the maximum
202- write bandwidth that may be used for recoveries if
203- `indices.recovery.max_bytes_per_sec` and `node.bandwidth.recovery.factor.write`
204- are not set. Must be greater than `0` and not greater than `1`. If not set, the
186+ (float) The proportion of the maximum
187+ write bandwidth that may be used for recoveries if `indices.recovery.max_bytes_per_sec`
188+ is not set. Must be greater than `0` and not greater than `1`. If not set, the
205189value of `node.bandwidth.recovery.operator.factor` is used. If no factor
206- settings are set then the value `0.4` is used. When the {operator-feature} is
207- enabled, this setting can be updated only by operator users.
190+ settings are set then the value `0.4` is used.
208191
209192`node.bandwidth.recovery.operator.factor`::
210- (float, <<dynamic-cluster-setting,dynamic>> ) The proportion of the maximum
193+ (float) The proportion of the maximum
211194bandwidth that may be used for recoveries if neither
212195`indices.recovery.max_bytes_per_sec` nor any other factor settings are set.
213- Must be greater than `0` and not greater than `1`. Defaults to `0.4`. When the
214- {operator-feature} is enabled, this setting can be updated only by operator
215- users.
196+ Must be greater than `0` and not greater than `1`. Defaults to `0.4`.
216197
217198`node.bandwidth.recovery.operator.factor.max_overcommit`::
218- (float, <<dynamic-cluster-setting,dynamic>> ) The proportion of the absolute
199+ (float) The proportion of the absolute
219200maximum bandwidth that may be used for recoveries regardless of any other
220- settings. Must be greater than `0`. Defaults to `100`. When the
221- {operator-feature} is enabled, this setting can be updated only by operator
222- users.
201+ settings. Must be greater than `0`. Defaults to `100`.
0 commit comments