Bug 1969895 - Collectd memory consumption is growing gradually causing 'out of memory' issue on nodes.
Summary: Collectd memory consumption is growing gradually causing 'out of memory' issu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z7
: 16.1 (Train on RHEL 8.2)
Assignee: Matthias Runge
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 2007255
TreeView+ depends on / blocked
 
Reported: 2021-06-09 12:28 UTC by Matthias Runge
Modified: 2021-12-09 21:45 UTC (History)
10 users (show)

Fixed In Version: openstack-tripleo-heat-templates-11.3.2-1.20210628063306.29a02c1.el8ost
Doc Type: Release Note
Doc Text:
With this update, the memory limit for the `collectd` container has been increased to 512 MB. When this limit is exceeded, the container restarts.
Clone Of: 1966428
: 2007255 (view as bug list)
Environment:
Last Closed: 2021-12-09 20:19:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-4485 0 None None None 2021-11-18 11:32:59 UTC
Red Hat Product Errata RHBA-2021:3762 0 None None None 2021-12-09 20:19:59 UTC

Comment 5 Matthias Runge 2021-06-11 14:42:52 UTC 
Submitted https://review.opendev.org/c/openstack/tripleo-heat-templates/+/796026
Comment 7 Matthias Runge 2021-06-18 06:00:33 UTC 
The upstream patch has two approval votes from core reviewers. Unfortunately, the CI is not happy (unrelated to the patch). I can not move forward with providing a hot-fix without having the code merged at least to the master branch upstream.
Comment 8 Matthias Runge 2021-06-24 07:04:43 UTC 
the backport to train has finally merged https://review.opendev.org/c/openstack/tripleo-heat-templates/+/797704
Comment 11 Matthias Runge 2021-06-28 06:58:44 UTC 
How to test:
podman inspect collectd | grep Memory

should show a limit for "Memory", if it shows 0, there is no limit set.
Comment 18 Leonid Natapov 2021-08-10 14:50:54 UTC 
root@ctrl-0-16-1 collectd]# podman inspect collectd | grep Memory 

"Memory": 536870912, 
"KernelMemory": 0, 
"MemoryReservation": 0, 
"MemorySwap": 1073741824, 
"MemorySwappiness": -1,
Comment 28 Peter Hardon 2021-11-03 14:15:39 UTC 
Please take a look at this commit which might fix the source of the issue (no collectd container restarts)
Would it be possible to backport it to train (RHOSP 16.1)?
https://github.com/collectd/collectd/commit/e7dd149f6f8279d844d172663023a841aa032a93

Thx,
Peter
Comment 30 Matthias Runge 2021-11-22 09:43:03 UTC 
(In reply to Peter Hardon from comment #28)
> Please take a look at this commit which might fix the source of the issue
> (no collectd container restarts)
> Would it be possible to backport it to train (RHOSP 16.1)?
> https://github.com/collectd/collectd/commit/
> e7dd149f6f8279d844d172663023a841aa032a93
> 
> Thx,
> Peter

Hi Peter,

the commit has been included in collectd for OSP since OSP 13. It is possible (and recommended to set the value).
Comment 37 errata-xmlrpc 2021-12-09 20:19:41 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 (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement 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-2021:3762
Note You need to log in before you can comment on or make changes to this bug.