| Clement_Goubert | |
| Feb 25 2026, 2:58 PM |
| F72412425: statsd_exporter_metrics_increasing.png | |
| Feb 25 2026, 3:08 PM |
| F72411537: image.png | |
| Feb 25 2026, 2:58 PM |
statsd-exporter ramps RAM consumption up over around a week then gets OOMKilled.
Figure out if this is overload or a memory leak:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| statsd-exporter: Add 2 replicas for mw-web | operations/deployment-charts | master | +1 -1 |
Change #1243846 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/deployment-charts@master] statsd-exporter: Add 2 replicas for mw-web
Since this behaviour was apparent on multiple mw-on-k8s deployments, and disappeared with more replicas, it's very likely that it's load related and not an actual memory leak. This should be confirmed if we get either longer time to oomkill or the behaviour disappears with more replicas. If the behaviour disappears, no more changes should be needed. If the time to oomkill is longer, we should raise the memory limits until the asymptote reached by the RAM usage curves doesn't hit the limit.
The number of metrics statsd-exporter is reporting seems to be increasing similarly over the lifetime of the container:
Change #1243846 merged by jenkins-bot:
[operations/deployment-charts@master] statsd-exporter: Add 2 replicas for mw-web