Skip to content

[enterprise-4.5] BZ1846458 - Remove note that ES scaling is not supported #28017

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
Dec 9, 2020
Merged

[enterprise-4.5] BZ1846458 - Remove note that ES scaling is not supported #28017

Show file tree
Hide file tree
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
17 changes: 5 additions & 12 deletions logging/config/cluster-logging-log-store.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,22 +11,16 @@ You can make modifications to your log store, including:

* storage for your Elasticsearch cluster
* shard replication across data nodes in the cluster, from full replication to no replication
* external access to Elasticsearch data

[NOTE]
====
Scaling down Elasticsearch nodes is not supported. When scaling down, Elasticsearch pods can be accidentally deleted,
possibly resulting in shards not being allocated and replica shards being lost.
====
* external access to Elasticsearch data

//Following paragraph also in modules/cluster-logging-deploy-storage-considerations.adoc

Elasticsearch is a memory-intensive application. Each Elasticsearch node needs 16G of memory for both memory requests and limits,
unless you specify otherwise in the `ClusterLogging` custom resource. The initial set of {product-title} nodes might not be large enough
Elasticsearch is a memory-intensive application. Each Elasticsearch node needs 16G of memory for both memory requests and limits,
unless you specify otherwise in the `ClusterLogging` custom resource. The initial set of {product-title} nodes might not be large enough
to support the Elasticsearch cluster. You must add additional nodes to the {product-title} cluster to run with the recommended
or higher memory.
or higher memory.

Each Elasticsearch node can operate with a lower memory setting though this is not recommended for production environments.
Each Elasticsearch node can operate with a lower memory setting, though this is not recommended for production environments.


// The following include statements pull in the module files that comprise
Expand Down Expand Up @@ -55,4 +49,3 @@ include::modules/cluster-logging-elasticsearch-persistent-storage-empty.adoc[lev
include::modules/cluster-logging-manual-rollout-rolling.adoc[leveloffset=+1]

include::modules/cluster-logging-elasticsearch-exposing.adoc[leveloffset=+1]

7 changes: 3 additions & 4 deletions modules/cluster-logging-elasticsearch-scaledown.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,11 @@
[id="cluster-logging-elasticsearch-scaledown_{context}"]
= Scaling down Elasticsearch pods

Reducing the number of Elasticsearch pod in your cluster can result in data loss or Elasticsearch performance degradation.
Reducing the number of Elasticsearch pods in your cluster can result in data loss or Elasticsearch performance degradation.

If you scale down, you should scale down by one pod at a time and allow the cluster to re-balance the shards and replicas. After the Elasticsearch health status returns to `green`, you can scale down by another pod.
If you scale down, you should scale down by one pod at a time and allow the cluster to re-balance the shards and replicas. After the Elasticsearch health status returns to `green`, you can scale down by another pod.

[NOTE]
====
If your Elasticsearch cluster is set to `ZeroRedundancy`, you should not scale down your Elasticsearch pods.
If your Elasticsearch cluster is set to `ZeroRedundancy`, you should not scale down your Elasticsearch pods.
====