Configuring CPU and memory limits for OpenShift Logging components

You can configure both the CPU and memory limits for each of the OpenShift Logging components as needed.

Configuring CPU and memory limits

The OpenShift Logging components allow for adjustments to both the CPU and memory limits.

Procedure

  1. Edit the ClusterLogging custom resource (CR) in the openshift-logging project:

    1. $ oc -n openshift-logging edit ClusterLogging instance
    1. apiVersion: "logging.openshift.io/v1"
    2. kind: "ClusterLogging"
    3. metadata:
    4.   name: "instance"
    5.   namespace: openshift-logging
    7. ...
    9. spec:
    10.   managementState: "Managed"
    11.   logStore:
    12.     type: "elasticsearch"
    13.     elasticsearch:
    14.       nodeCount: 3
    15.       resources: (1)
    16.         limits:
    17.           memory: 16Gi
    18.         requests:
    19.           cpu: 200m
    20.           memory: 16Gi
    21.       storage:
    22.         storageClassName: "gp2"
    23.         size: "200G"
    24.       redundancyPolicy: "SingleRedundancy"
    25.   visualization:
    26.     type: "kibana"
    27.     kibana:
    28.       resources: (2)
    29.         limits:
    30.           memory: 1Gi
    31.         requests:
    32.           cpu: 500m
    33.           memory: 1Gi
    34.       proxy:
    35.         resources: (2)
    36.           limits:
    37.             memory: 100Mi
    38.           requests:
    39.             cpu: 100m
    40.             memory: 100Mi
    41.       replicas: 2
    42.   collection:
    43.     logs:
    44.       type: "fluentd"
    45.       fluentd:
    46.         resources: (3)
    47.           limits:
    48.             memory: 736Mi
    49.           requests:
    50.             cpu: 200m
    51.             memory: 736Mi
    1Specify the CPU and memory limits and requests for the log store as needed. For Elasticsearch, you must adjust both the request value and the limit value.
    2Specify the CPU and memory limits and requests for the log visualizer as needed.
    3Specify the CPU and memory limits and requests for the log collector as needed.