B/SBuildSift
Evidence intelligence desk
Back to candidates

logging / fluentd

fluentd consumes too much memory (ooms)

fluentd consumes too much memory (ooms)

Problem statement normalized from the linked evidence
CANDIDATE VIEW · NOT A PUBLISHED OPPORTUNITY
01

Qualification checklist

Gate decision: Aug 15, 2026

×
At least 3 independent users2 / 3
NOT MET
At least 2 independent discussions2 / 2
MET
At least 1 supporting signal1 Blocked workflows · Persistence
MET
02

Observed signals

Users2
Discussions2
Mentions2
Active days2
Source coverageGitHub
TrendUNKNOWN
First seenJul 22, 2016
Last seenOct 07, 2016

Why the gate is holding

  • Fewer than 3 independent users

Competition research, commercial scoring, and Build Gap analysis do not run until this gate passes.

03

Source evidence

2 evidence records

github · HIGH · Oct 07, 2016

Load tests of logging pipeline

Kubernetes users raised a bunch of issues with monitoring pipeline. The most common is that fluentd tends to OOM even with moderate load (ref #29411). In order to fixed those problems first we need to perform load test of monitoring pipeline. The work items: - [x] design and implement a tool for logging load tests - [x] benchmark fluentd+GCL pipeline - [ ] benchmark fluentd+ES pipeline - [x] setup automatic tests
BUGBLOCKED WORKFLOW

piosz · kubernetes/kubernetes

View original

github · HIGH · Jul 22, 2016

fluentd ooms too much

@jimmidyson any ideas? It's a pig.
COMPLAINT

bprashanth · kubernetes/kubernetes

View original