Skip to content

Add Async Batch Shard Settings #7056

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 6 commits into from
May 8, 2024
Merged

Add Async Batch Shard Settings #7056

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ebf2178
Add Async Batch Shard Settings
Pranshu-S Apr 30, 2024
108989a
Addressing suggestions to wording.
Pranshu-S May 3, 2024
bc2af5c
Addressing suggestions to wording.
Pranshu-S May 6, 2024
999edf2
Apply suggestions from code review
Naarcha-AWS May 7, 2024
11d77a4
Apply suggestions from code review
Naarcha-AWS May 7, 2024
a4a1ae6
Apply suggestions from code review
Naarcha-AWS May 7, 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
2 changes: 2 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 @@ -96,6 +96,8 @@ OpenSearch supports the following cluster-level routing and shard allocation set
- `REPLICA_FIRST` – Replica shards are relocated first, before primary shards. This prioritization may help prevent a cluster's health status from going red when carrying out shard relocation in a mixed-version, segment-replication-enabled OpenSearch cluster. In this situation, primary shards relocated to OpenSearch nodes of a newer version could try to copy segment files to replica shards on an older version of OpenSearch, which would result in shard failure. Relocating replica shards first may help to avoid this in multi-version clusters.
- `NO_PREFERENCE` – The default behavior in which the order of shard relocation has no importance.

- `cluster.allocator.gateway.batch_size` (Integer): Limits the number of shards sent to data nodes in one batch for fetching any unassigned shard metadata. Default is `2000`.
- `cluster.allocator.existing_shards_allocator.batch_enabled` (Boolean): Enables batch allocation of unassigned shards that already exist on the disk as opposed to allocating one shard at a time. This reduces memory and transport overhead by fetching any unassigned shard metadata in a batch call. Default is `false`.
## Cluster-level shard, block, and task settings

OpenSearch supports the following cluster-level shard, block, and task settings:
Expand Down