Bug 1488001 - [3.4.1 Documentation]Add one troubleshooting for OutOfMemory error in kibana-proxy container
Summary: [3.4.1 Documentation]Add one troubleshooting for OutOfMemory error in kibana-...
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-04 05:45 UTC by Junqi Zhao
Modified: 2019-08-10 06:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-10 06:46:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Junqi Zhao 2017-09-04 05:45:22 UTC
Document URL: 
https://docs.openshift.com/container-platform/3.4/install_config/aggregate_logging.html

Section Number and Name: 
https://docs.openshift.com/container-platform/3.4/install_config/aggregate_logging.html#troubleshooting-kibana

Describe the issue: 
Add one kibana troubleshooting issue
OutOfMemory error in kibana-proxy container

kibana-proxy container, default value for resources.limits.memory is 96Mi, sometimes kibana pods will terminated for OutOfMemory error.
To fix this issue, you could use the following script to change resources.limits.memory from default value 96Mi to 256Mi for kibana-proxy 

for dc in $(oc get deploymentconfig --selector logging-infra=kibana -o name); do
    oc scale $dc --replicas=0
    oc patch $dc \
       -p '{"spec":{"template":{"spec":{"containers":[{"name":"kibana-proxy","resources":{"limits":{"memory": "256Mi"}}}]}}}}'
    oc rollout latest $dc
    oc scale $dc --replicas=1
done

Suggestions for improvement: 

Additional information:


Note You need to log in before you can comment on or make changes to this bug.