-
Notifications
You must be signed in to change notification settings - Fork 77
Set FluentBit self logs to buffer in memory instead of filesystem #631
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
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
33bef92 to
989db22
Compare
fb594fb to
cb9339e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
SLES 12 was failing, but it's not related to this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a doc somewhere I can read on why we want to do this?
(Also, presumably fluent-bit is still writing state somewhere on disk so it doesn't reprocess the same log lines, right?)
Added comment for clarification on the in memory switch
# Conflicts: # confgenerator/logging_receivers.go
Parameterized
storage.typeconfig with variableBufferInMemory. Edit component to always use in memory buffering for self logsFollowing: http://b/226668416, this PR changes self logs to buffer in memory as opposed to the filesystem.
Soak Test:
