Bug 1488001

Summary: [3.4.1 Documentation]Add one troubleshooting for OutOfMemory error in kibana-proxy container
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED EOL QA Contact: Vikram Goyal <vigoyal>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.4.1CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-10 06:46:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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: