How to determine mem_buf_limit, container memory when OUTPUT is DOWN. #9420
Unanswered
sasikiranvaddi
asked this question in
Q&A
Replies: 2 comments
-
Hi, Any suggestions on this ticket? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi, Any suggestions on this ticket? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi
Fluent-Bit: 3.0.5
We have inputs one harvests fluent-bit logs and the other is from the a different service /logs/gen0.log(Throughput: 10 logs/min of size 150bytes)
The mem_buf_limit is set as 500KB for both the inputs and storage.type is default i.e., memory. (more interested with storage.type as memory, as with filesystem the chunks are backed up in disk, the memory consumption looks normal in unpredictable conditions)
100Mi is set as a memory limit for the container that is running fluent-bit.
We have observed when the outputs are available, the mem_buf usage is normal and there are no issues. But when the output is down we observe OOMKILL has been triggered before mem_cache getting filled. As a workaround to prevent OOMKILL, there is a recommendation provided in the community1 to lower the mem_buf_limit, but it has inter dependency with the throughput
Fluent-Bit.conf
bash-4.4$ cat /etc/fluent-bit/fluent-bit.conf
@include /etc/fluent-bit/inputs.conf
@include /etc/fluent-bit/outputs.conf
@include /etc/fluent-bit/filters.conf
inputs.conf
Beta Was this translation helpful? Give feedback.
All reactions