Fluentd config: turn off S3 bucket checks #1999
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Turn off the feature to create the S3 bucket and to check for S3 bucket existance at startup. The logging-agent doesn't have permission to create S3 buckets, and the check causes the Fluentd worker to fail and restart if the bucket is not present. Constant restarting leads to high CPU consumption. Instead we choos to keep the worker running and try to ship logs to S3. This will fail if the bucket does not exist, but the buffer size is limited and we can alert on buffer size and errors and the CPU consumption stays low. Signed-off-by: Christian Berg <[email protected]>
|
👍 |
1 similar comment
|
👍 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Turn off the feature to create the S3 bucket and to check for S3
bucket existence at startup. The logging-agent doesn't have permission
to create S3 buckets, and the check causes the Fluentd worker to fail
and restart if the bucket is not present. Constant restarting leads to
high CPU consumption.
Instead we choose to keep the worker running and try to ship logs to
S3. This will fail if the bucket does not exist, but the buffer size
is limited and we can alert on buffer size and errors and the CPU
consumption stays low.