Bug 1381610

Summary:	Metadata Proxy Memory Growth
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	openstack-neutron	Assignee:	Daniel Alvarez Sanchez <dalvarez>
Status:	CLOSED ERRATA	QA Contact:	Toni Freger <tfreger>
Severity:	medium	Docs Contact:
Priority:	high
Version:	10.0 (Newton)	CC:	amuller, chrisw, ihrachys, jtaleric, nyechiel, srevivo, tvignaud
Target Milestone:	ga	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-11.0.0-0.20170624003801.11acb1d.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 20:46:56 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 Sai Sindhur Malleni 2016-10-04 14:38:57 UTC

Description of problem:
When launching 1500 routers using Browbeat ( which orchestrates rally ) we see metadata proxy growing to 29 Gb in RSS on the controller. 

Version-Release number of selected component (if applicable):
RHOP 10


How reproducible: 100%


Steps to Reproduce:
1. Launch large number of routers
2. Observe memory growth of metadata proxy process
3.

Actual results:
Chart showing memory growth when 1500 routers are launched in all at a concurrency of 96 using rally.

https://hurl.corp.redhat.com/metadata-proxy-memory

Expected results:


Additional info:

Comment 1 Assaf Muller 2017-04-26 10:17:40 UTC

All patches have been merged upstream.

Comment 2 Daniel Alvarez Sanchez 2017-04-26 10:22:42 UTC

Downstream patches (OSP10 and OSP11) are stuck until OSP11 GA is released. Patch for OSP11 will go into Z-stream and then we'll backport it into OSP10.

Comment 9 errata-xmlrpc 2017-12-13 20:46:56 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, 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/RHEA-2017:3462