Increase fluent-bit flush interval to lessen DNS load #319
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
samjsong
approved these changes
Nov 26, 2019
maimaisie
approved these changes
Nov 26, 2019
|
I think we decreased it to 1s to avoid aother issue? @samjsong Did you remember? |
|
I believe that was the |
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.
Description
From the CoreDNS investigation, we are using the default fluent-bit flush interval of 1s, which leads to DNS lookup per flush. We can increase the flush interval to lessen the DNS lookups, and also the number of network calls from fluent-bit to fluentd.
Testing performed