From dfb0a479078d5126e82b52b8b682a687507bb90c Mon Sep 17 00:00:00 2001 From: libander Date: Fri, 12 Nov 2021 10:35:38 -0500 Subject: [PATCH] Manual CP of https://github.com/openshift/openshift-docs/pull/38755 to 4.10 --- modules/cluster-logging-logstore-limits.adoc | 27 +++++++++++--------- 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/modules/cluster-logging-logstore-limits.adoc b/modules/cluster-logging-logstore-limits.adoc index 6d77424065c7..fb4885ecf320 100644 --- a/modules/cluster-logging-logstore-limits.adoc +++ b/modules/cluster-logging-logstore-limits.adoc @@ -40,14 +40,14 @@ metadata: spec: logStore: type: "elasticsearch" - elasticsearch: - resources: <1> - limits: - memory: 16Gi - requests: + elasticsearch:<1> + resources: + limits: <2> + memory: "32Gi" + requests: <3> cpu: "1" - memory: "64Gi" - proxy: <2> + memory: "16Gi" + proxy: <4> resources: limits: memory: 100Mi @@ -56,22 +56,25 @@ spec: ---- <1> Specify the CPU and memory requests for Elasticsearch as needed. If you leave these values blank, the OpenShift Elasticsearch Operator sets default values that should be sufficient for most deployments. The default values are `16Gi` for the memory request and `1` for the CPU request. -<2> Specify the CPU and memory requests for the Elasticsearch proxy as needed. If you leave these values blank, the OpenShift Elasticsearch Operator sets default values that should be sufficient for most deployments. The default values are `256Mi` for the memory request and `100m` for the CPU request. +<2> The maximum amount of resources a pod can use. +<3> The minimum resources required to schedule a pod. +<4> Specify the CPU and memory requests for the Elasticsearch proxy as needed. If you leave these values blank, the OpenShift Elasticsearch Operator sets default values that are sufficient for most deployments. The default values are `256Mi` for the memory request and `100m` for the CPU request. -If you adjust the amount of Elasticsearch memory, you must change both the request value and the limit value. +When adjusting the amount of Elasticsearch memory, the same value should be used for both `requests` and `limits`. For example: [source,yaml] ---- resources: - limits: + limits: <1> memory: "32Gi" - requests: + requests: <2> cpu: "8" memory: "32Gi" ---- +<1> The maximum amount of the resource. +<2> The minimum amount required. Kubernetes generally adheres the node configuration and does not allow Elasticsearch to use the specified limits. Setting the same value for the `requests` and `limits` ensures that Elasticsearch can use the memory you want, assuming the node has the memory available. -