+++ This bug was initially created as a clone of Bug #1861715 +++ Description of problem: https://github.com/collectd/collectd/commit/e7dd149f6f8279d844d172663023a841aa032a93 added the SendQueueLimit option for the amqp1 plugin, which helps with collectd memory usage. https://github.com/voxpupuli/puppet-collectd/pull/950 adds the support This bz is to track the option to downstream
How to test: In an environment file add:: ExtraConfig: collectd::plugin::amqp1::send_queue_limit: 40 and observe if this parameter SendQueueLimit is added to /etc/collectd.d/10-amqp1.conf You should also be able to shut off your stf (or stop the route) and you should not see collectd memory usage going up.
# Generated by Puppet <LoadPlugin amqp1> Globals false Interval 5 </LoadPlugin> <Plugin amqp1> <Transport "metrics"> Host "172.17.3.126" Port "5666" User "guest" Password "guest" Address "collectd" RetryDelay 1 SendQueueLimit 40 <Instance "notify"> Format "JSON" Notify true PreSettle false </Instance> <Instance "telemetry"> Format "JSON" PreSettle false </Instance> </Transport> </Plugin> collectd memory remains stable
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 13.0 director bug fix 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-2020:4388