Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1357057

Summary:	atomic-openshift-master.service memory leak
Product:	OpenShift Container Platform	Reporter:	Steven Walter <stwalter>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED DUPLICATE	QA Contact:	DeShuai Ma <dma>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.2.1	CC:	agoldste, aos-bugs, jokerman, mmccomas, tstclair
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:	2016-07-22 15:01:50 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 Steven Walter 2016-07-15 15:20:11 UTC

Description of problem:
Customer has one master, two nodes. Sees the memory usage of atomic-openshift-master.service increase steadily over time until it is using about 3 GiB memory and starts to see degradation of web console, timeouts, etc. Memory increase seems independent of current builds, interaction, etc. Restarting the service once or twice a day alleviates the issue, but it eventually grows again.

Version-Release number of selected component (if applicable):
3.2.1.1  environment with Docker 1.9.1 on RHEV. GlusterFS is used for persistent volumes.

How reproducible:
Not yet reproduced

Additional info:
Customer has provided heapdumps and logs, which can be attached.

Comment 2 Timothy St. Clair 2016-07-21 19:34:45 UTC

1. What is the size of the image that is running the daemon?  recommendations (https://docs.openshift.org/latest/install_config/install/prerequisites.html)
2. What does the memory cap at? 
3. Please grab a heap profile : https://ekuric.wordpress.com/tag/golang/

Comment 3 Andy Goldstein 2016-07-22 15:01:50 UTC

Seth looked at the heap profile attached to the support case. It is identical to what we're seeing in https://bugzilla.redhat.com/show_bug.cgi?id=1323733. Marking this a duplicate.

*** This bug has been marked as a duplicate of bug 1323733 ***