Skip to content
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

Jump to bottom

Add documentation for primary rebalancing #7059

Merged
merged 4 commits into from
May 2, 2024
Merged

Add documentation for primary rebalancing #7059

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
62a997a
Add documentation for primary rebalacing
Arpit-Bandejiya Apr 30, 2024
799175f
Update _install-and-configure/configuring-opensearch/cluster-settings.md
Naarcha-AWS May 2, 2024
c242470
Apply suggestions from code review
Naarcha-AWS May 2, 2024
7f74b3b
Merge branch 'main' into main
Naarcha-AWS May 2, 2024
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: 4 additions & 0 deletions _install-and-configure/configuring-opensearch/cluster-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,10 @@ OpenSearch supports the following cluster-level routing and shard allocation set

- `cluster.routing.allocation.balance.prefer_primary` (Boolean): When set to `true`, OpenSearch attempts to evenly distribute the primary shards between the cluster nodes. Enabling this setting does not always guarantee an equal number of primary shards on each node, especially in the event of failover. Changing this setting to `false` after it was set to `true` does not invoke redistribution of primary shards. Default is `false`.

- `cluster.routing.allocation.rebalance.primary.enable` (Boolean): When set to `true`, OpenSearch attempts to evenly rebalance the primary shards between the cluster nodes. Enabling this setting, cluster tries to maintain number of primary shards on each node with maximum buffer defined by `cluster.routing.allocation.rebalance.primary.buffer`. Changing this setting to `false` after it was set to `true` does not invoke redistribution of primary shards. Default is `false`.
Naarcha-AWS marked this conversation as resolved.
Show resolved Hide resolved

- `cluster.routing.allocation.rebalance.primary.buffer` (Floating point): Defines the maximum allowed buffer of primary shards between nodes when `cluster.routing.allocation.rebalance.primary.enable` is enabled. Default is `0.1`.

- `cluster.routing.allocation.disk.threshold_enabled` (Boolean): When set to `false`, disables the disk allocation decider. This will also remove any existing `index.blocks.read_only_allow_delete index blocks` when disabled. Default is `true`.

- `cluster.routing.allocation.disk.watermark.low` (String): Controls the low watermark for disk usage. When set to a percentage, OpenSearch will not allocate shards to nodes with that percentage of disk used. This can also be entered as ratio value, like `0.85`. Finally, this can also be set to a byte value, like `400mb`. This setting does not affect the primary shards of newly created indexes, but will prevent their replicas from being allocated. Default is `85%`.
Expand Down
Loading