Skip to content

Remove gateway recover after nodes setting #11596

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 1 commit into from
Nov 26, 2025
Merged

Remove gateway recover after nodes setting #11596

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
4 changes: 0 additions & 4 deletions _install-and-configure/configuring-opensearch/discovery-gateway-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,10 +79,6 @@ The following discovery settings are for expert-level configuration. **Warning**

The local gateway stores on-disk cluster state and shard data that is used when a cluster is restarted. The following local gateway settings are supported:

- `gateway.recover_after_nodes` (Static, integer): The minimum number of total nodes for any role that must be running after a full cluster restart before recovery can begin.
- **Default**: `0` (disabled)—recovery can start as soon as a cluster forms.
- **Recommendation**: Set to slightly over half of the number of all expected nodes so that the cluster doesn't start recovering with too few nodes.

- `gateway.recover_after_data_nodes` (Static, integer): The minimum number of data nodes that must be running after a full cluster restart before recovery can begin.
- **Default**: `0`
- **Recommendation**: Set to a significant portion of the data nodes—approximately 50–70% of the total data nodes—to avoid premature recovery.
Expand Down
Loading