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

Clarify high availability recommendations in Elasticsearch orchestration docs #8151

Merged
merged 3 commits into from
Oct 25, 2024
Merged

Clarify high availability recommendations in Elasticsearch orchestration docs #8151

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cb561a8
(Doc+) Rolling changes high availability is per ES data tier
stefnestor Oct 22, 2024
79c7dbd
Update docs/orchestrating-elastic-stack-applications/elasticsearch/or…
kilfoyle Oct 22, 2024
39757ad
feedback
stefnestor Oct 24, 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: 1 addition & 1 deletion docs/orchestrating-elastic-stack-applications/elasticsearch/orchestration.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ Due to relying on Kubernetes primitives such as StatefulSets, the ECK orchestrat
** Single-node clusters
** Clusters containing indices with no replicas

If an Elasticsearch node holds the only copy of a shard, this shard becomes unavailable while the node is upgraded. Clusters with more than one node and at least one replica per index are recommended.
If an {es} node holds the only copy of a shard, this shard becomes unavailable while the node is upgraded. link:{ref}/high-availability-cluster-design.html[Highly available] clusters are recommended, including having more than one node per link:{ref}/data-tiers.html[data tier] and at least one replica per index.
stefnestor marked this conversation as resolved.
Show resolved Hide resolved

* Elasticsearch Pods may stay `Pending` during a rolling upgrade if the Kubernetes scheduler cannot re-schedule them back. This is especially important when using local PersistentVolumes. If the Kubernetes node bound to a local PersistentVolume does not have enough capacity to host an upgraded Pod which was temporarily removed, that Pod will stay `Pending`.

Expand Down