Description of problem:
If overcloud is deployed with collectd but when collectd is not configured to use any write plugin or any destination collectd server it can send data, memory leak is noticed.
Collectd processes Resident memory increases to 20GB in few hours.
During every cycle collectd collects data, the process visibly grows in memory usage.
Collectd should have some configuration to discard collected data rather than storing it in memory when it is not configured with destination collectd server or write plugin.
Version-Release number of selected component (if applicable):
RHOS15z1
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
This has been lowered to medium since it only affects already-broken installations. Fixes are required upstream and they won't happen in time for 15z2; adjusting milestone accordingly.
I've been hammering on collectd with WriteQueueLimitHigh and WriteQueueLimitLow set (and I believe Matthias has, also), and those seem sufficient to control the memory usage. We may want to set some reasonable defaults to the collectd container's default collectd params.