-
Notifications
You must be signed in to change notification settings - Fork 2
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
Log group class Support => aws distro cherry pick #31
base: 2.32.2-all-cherry-picks
Are you sure you want to change the base?
Conversation
1426fc8
to
4f543c0
Compare
Signed-off-by: Wesley Pettit <[email protected]>
4f543c0
to
d4a6e26
Compare
|
OperationAbortedException with log_group_class: Race Condition between Fluent Bit instancesBelow is normal even if the log_group_class was successfully set.
A k8s cluster usually has > 1 node and Fluent Bit is run as a daemonset. On startup, every daemon will try to set the logGroupClass, but only one can succeed and create the group. Thus, the above messages will be printed by individual Fluent Bit instances that failed. The succeeding instance would print:
Search CloudWatch Log Insights for the above to determine if one instance succeeded in setting the log group class because it created the group. Workaround: Create Log Group before deploymentThe best practice workaround is to create log groups before deployment; generally at cluster creation time. Each Fluent Bit instance will not need to create the group. You can disable group creation with |
Upstream: fluent#8832 |
Enter
[N/A]
in the box, if an item is not applicable to your change.Testing
Before we can approve your change; please submit the following in a comment:
If this is a change to packaging of containers or native binaries then please confirm it works for all targets.
Documentation
Backporting
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.