Bug 1894632

Summary:	Proxy container in elasticsearch pods restarting due to oom-kill during test of scale cluster [4.5.z]
Product:	OpenShift Container Platform	Reporter:	Simon Reber <sreber>
Component:	Logging	Assignee:	Vimal Kumar <vimalkum>
Status:	CLOSED ERRATA	QA Contact:	Eric Matysek <ematysek>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.5	CC:	agurenko, anli, aos-bugs, ematysek, ewolinet, jcantril, periklis, vimalkum
Target Milestone:	---	Keywords:	Regression
Target Release:	4.5.z
Hardware:	x86_64
OS:	Linux
Whiteboard:	logging-core
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1856502	Environment:
Last Closed:	2020-11-24 12:54:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1856502
Bug Blocks:	1860084

Comment 4 Vimal Kumar 2020-11-06 09:58:41 UTC

@simon.reber , i have opened a PR for CLO

Comment 6 Anping Li 2020-11-13 08:34:03 UTC

@Eric Matysek, Could you check if this had been fixed in 4.5?

Comment 8 Eric Matysek 2020-11-19 19:38:06 UTC

Verified in 4.5
I am able to configure proxy memory resources in the clusterlogging spec like so
    elasticsearch:
      proxy:
        resources:
          requests:
            memory: 256Mi
          limits:
            memory: 256Mi

Comment 10 errata-xmlrpc 2020-11-24 12:54:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5.20 extras update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5120