You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrade fluentd from 1.15.2 to 1.17.0, fluentd (es output) encountered memory reclaim issue in complex fault scenarios.
memory is not released when ES status is crashloopback and fluentd is retring to push buffered log.
Steps to replicate
env prepare
start elastic cluster, nginx proxy for elastic, fluentd with ES output (fluentd ES outputs to nginx ip, nginx reserve-proxy to ES cluster)
fault simulation
a. config nginx to return 502 and reload nginx. (or stop nginx)
b. wait fluentd to generate at least 2 buffer files (buffer.b..., buffer.qaaa, bufer.qbbb...)
c. quickly revert step "a" and tail nginx log
d. when fluentd begin to retry pushing buffered log (see nginx _bulk http 200 log): redo step "a"
e. fluentd begin to output lots of error logs (for each log entry) and the memory of fluentd (v1.17.0) keeps increasing until OOM or container restart (liveness-probe: healthcheck failed), but old-version fluentd works well.
Problem
After upgrade fluentd from 1.15.2 to 1.17.0, fluentd (es output) encountered memory reclaim issue in complex fault scenarios.
memory is not released when ES status is crashloopback and fluentd is retring to push buffered log.
Steps to replicate
Configs
main nginx(openresty) config
fluentd config
error logs
log generator
Expected Behavior or What you need to ask
Why
Using Fluentd and ES plugin versions
almalinux 9.4
k8s 1.26
fluentd 1.17.0 & fluentd 1.15.2
7.17.6
requests 256Mi, limits 512Mi
monitor
The text was updated successfully, but these errors were encountered: