Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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 logging/config/cluster-logging-log-store.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ include::modules/cluster-logging-logstore-limits.adoc[leveloffset=+1]

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

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

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

include::modules/cluster-logging-elasticsearch-persistent-storage-empty.adoc[leveloffset=+1]
Expand Down
16 changes: 16 additions & 0 deletions modules/cluster-logging-elasticsearch-scaledown.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
// Module included in the following assemblies:
//
// * logging/cluster-logging-log-store.adoc

[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.

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.
====