Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forward input + multi-line parser consumes more than 100% CPU and lost of enriched data #8702

Closed
quanghungb opened this issue Apr 11, 2024 · 6 comments

Comments

@quanghungb
Copy link

Bug Report

During the evaluation of Fluent Bit, I am trying to have the following architecture (critical for our use case):
|fluent-bit-shipper| -> |fluent-bit-aggregator| -> |final destination|

But I got those 2 blocking issues:

  • CPU high usage (more than 100%)
  • Lost of enriched data (that have been done at the source)

Everything (configurations, instructions to reproduce, observations) provided here:

(I also shared this issue with Eduardo and Anurag as they asked)

Thanks for your help & feedback

@drbugfinder-work
Copy link
Contributor

Maybe related: #8473

@drbugfinder-work
Copy link
Contributor

@drbugfinder-work FYI I just tried with the latest version 3.0.2 and still observed the same issues :(

Does it make a difference, when you disable the multiline or/and the regex filter? Can you isolate the issue further?

@quanghungb
Copy link
Author

@drbugfinder-work FYI I tried the newest version 3.0.2 and can observe the same issues:

  • CPU usage growing up over 100% after few moment
  • the enriched data are still missing

Regarding your question about the multiline parser/regex, the issues appear only with forward input, because with the tail input everything is working well

@quanghungb
Copy link
Author

quanghungb commented Apr 20, 2024

hey @drbugfinder-work I was running the same scenario (with the latest 3.0.2) on my Macbook Air (much less power than my workstation) and did not see the issues (the CPU usage stays low and the enriched data are present in the output).
So I assumes that on my Macbook Air the throughput is less important so it does not flood the aggregator forward input.

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Jul 20, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants