Bug 1378245 - Mongod is allowed to use as much memory as it wants by default
Summary: Mongod is allowed to use as much memory as it wants by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: z1
: 11.0 (Ocata)
Assignee: Pradeep Kilambi
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 22:15 UTC by Graeme Gillies
Modified: 2017-07-19 17:04 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-6.1.0-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-19 17:04:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 455305 0 None None None 2017-04-10 12:37:23 UTC
OpenStack gerrit 455306 0 None None None 2017-04-10 12:37:58 UTC
RDO 6216 0 None None None 2017-04-10 12:51:15 UTC
Red Hat Product Errata RHBA-2017:1778 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 director Bug Fix Advisory 2017-07-19 21:01:28 UTC

Description Graeme Gillies 2016-09-21 22:15:38 UTC 
Hi,

A default RHOS 7 installation by director does not impose any limits on how much memory mongod can use. While this is perfectly normal for how mongod is expected to work, I think practically we need to introduce some kind of "safety" memory limit just in case. While mongod is supposed to be a good citizen and release memory when needed, it would be great to leverage the operating system to keep it in check "just in case".

Regards,

Graeme
Comment 3 Jon Schlueter 2017-04-11 19:27:15 UTC 
puppet-systemd-0.4.0-2.el7ost
Comment 4 Pradeep Kilambi 2017-04-18 20:25:30 UTC 
patches backported to stable/ocata and new puppet-systemd built in ocata
Comment 9 errata-xmlrpc 2017-07-19 17:04: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/RHBA-2017:1778
Note You need to log in before you can comment on or make changes to this bug.