Update fluent-bit submodule to v1.8.11 and switch dns resolver to legacy. #290
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
qingling128
added
the
kokoro:force-run
kokoro-team
removed
the
kokoro:force-run
qingling128
added
the
kokoro:force-run
kokoro-team
removed
the
kokoro:force-run
qingling128
force-pushed
the
lingshi-update-fluent-bit-1-8-11
branch
from
9a928b7 to
13b9f36
Compare
qingling128
force-pushed
the
lingshi-update-fluent-bit-1-8-11
branch
from
13b9f36 to
b1bb57b
Compare
jkschulz
approved these changes
Dec 16, 2021
qingling128
added
the
kokoro:force-run
kokoro-team
removed
the
kokoro:force-run
rafaelwestphal
pushed a commit
that referenced
this pull request
Dec 20, 2021
braydonk
pushed a commit
that referenced
this pull request
Dec 21, 2021
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.
When we upgrade to Fluent Bit
1.8.11, we ran into an issue fluent/fluent-bit#4300. Keeping the DNS resolver in legacy mode instead of the new async mode (introduced in1.8.5) to bypass it: http://b/203725238#comment40Test results look reasonable: http://b/203725238#comment41.
Also
