Skip to content

Expand Size your shards #4588

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
stefnestor merged 5 commits into from
Jan 18, 2026
Merged

Expand Size your shards #4588

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6a596c5
Expand Size your shards
tanja-milicic Jan 12, 2026
6a7003b
Merge branch 'main' into tanja-milicic-patch-1
kilfoyle Jan 12, 2026
d7f0f38
Update deploy-manage/production-guidance/optimize-performance/size-sh…
tanja-milicic Jan 18, 2026
017411d
Merge branch 'main' into tanja-milicic-patch-1
tanja-milicic Jan 18, 2026
bb1e0ab
fix link
tanja-milicic Jan 18, 2026
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: 1 addition & 1 deletion deploy-manage/production-guidance/optimize-performance/size-shards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@

### Shard distribution guidelines

To ensure that each node is working optimally, distribute shards evenly across nodes. Uneven distribution can cause some nodes to work harder than others, leading to performance degradation and instability.
{{es}} uses its [desired balance allocator](elasticsearch://reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings.md#shards-rebalancing-heuristics) to distribute shards across nodes based off heuristics for data stream writes, shard counts, and disk usage. Shard counts may end up unevenly distributed in order to evenly spread the node work. An [unbalanced cluster](/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md) may lead to performance degradation and instability, such as [watermark errors](/troubleshoot/elasticsearch/fix-watermark-errors.md). Poorly specified [sharding strategies](#create-a-sharding-strategy) may cause [hot spotting](/troubleshoot/elasticsearch/hotspotting.md).

Check notice on line 34 in deploy-manage/production-guidance/optimize-performance/size-shards.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.WordChoice: Consider using 'can, might' instead of 'may', unless the term is in the UI.

Check notice on line 34 in deploy-manage/production-guidance/optimize-performance/size-shards.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.WordChoice: Consider using 'can, might' instead of 'may', unless the term is in the UI.

Check notice on line 34 in deploy-manage/production-guidance/optimize-performance/size-shards.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.Wordiness: Consider using 'to' instead of 'in order to'.

Check notice on line 34 in deploy-manage/production-guidance/optimize-performance/size-shards.md

View workflow job for this annotation

GitHub Actions / preview / vale 

Elastic.WordChoice: Consider using 'can, might' instead of 'may', unless the term is in the UI.

While {{es}} automatically balances shards, you need to configure indices with an appropriate number of shards and replicas to allow for even distribution across nodes.

Expand Down
Loading