Bug 1381610 - Metadata Proxy Memory Growth
Summary: Metadata Proxy Memory Growth
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ga
: 12.0 (Pike)
Assignee: Daniel Alvarez Sanchez
QA Contact: Toni Freger
Depends On:
TreeView+ depends on / blocked
Reported: 2016-10-04 14:38 UTC by Sai Sindhur Malleni
Modified: 2018-02-05 19:02 UTC (History)
7 users (show)

Fixed In Version: openstack-neutron-11.0.0-0.20170624003801.11acb1d.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 20:46:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1524916 0 None None None 2016-10-04 14:46:20 UTC
OpenStack gerrit 431691 0 None None None 2017-04-26 10:17:40 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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):

How reproducible: 100%

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

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


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.


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