networking: add connection backoff config options#491
Closed
kabakaev wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Alexander Kabakaev <kabakaev@gmail.com>
kabakaev
force-pushed
the
connection-backoff-flb-pr3191
branch
from
1348b1e to
35f9324
Compare
Member
|
note: waiting on fluent/fluent-bit#3191 |
edsiper
added
the
waiting-for-user
eschabell
added
conflict
Collaborator
|
@esmerel would you mind reviewing this PR? I've nudged the owner on code PR fluent/fluent-bit#3191 which looks ready to merge. |
esmerel
reviewed
Oct 27, 2025
|
|
||
| ### Connection backoff | ||
|
|
||
| This set of options is designed for large-scale fluent-bit deployments, which may need to limit number of TCP SYN packets in case an output destination is unreachable. By default, fluent-bit will retry connecting to an output target on each chunk flush. But if, for example, `net.initial_backoff=8` and `net.max_backoff=60` options are set, then an output plugin will try to reconnect to a failing output only after a delay of 8, 16, 32 and 60 seconds. Each fluent-bit thread will keep trying only once every 60 seconds, until connection is healthy again. |
Contributor
There was a problem hiding this comment.
Suggested change
| This set of options is designed for large-scale fluent-bit deployments, which may need to limit number of TCP SYN packets in case an output destination is unreachable. By default, fluent-bit will retry connecting to an output target on each chunk flush. But if, for example, `net.initial_backoff=8` and `net.max_backoff=60` options are set, then an output plugin will try to reconnect to a failing output only after a delay of 8, 16, 32 and 60 seconds. Each fluent-bit thread will keep trying only once every 60 seconds, until connection is healthy again. | |
| This set of options is designed for large-scale Fluent Bit deployments, which may need to limit number of TCP SYN packets in case an output destination is unreachable. By default, Fluent Bit will retry connecting to an output target on each chunk flush. But if, for example, `net.initial_backoff=8` and `net.max_backoff=60` options are set, then an output plugin will try to reconnect to a failing output only after a delay of 8, 16, 32 and 60 seconds. Each Fluent Bit thread will keep trying only once every 60 seconds, until connection is healthy again. |
Contributor
There was a problem hiding this comment.
Looks generally ok to me as long as my suggestion is applied, but I can't see the conflicts to fix them.
eschabell
added
waiting-for-user
Collaborator
|
@kabakaev can you look at the review suggestions and conflicts so this is ready when code PR fluent/fluent-bit#3191 merges? |
eschabell
removed
the
waiting-for-user
eschabell
added
the
waiting-for-user
eschabell
added
Stale
and removed
waiting-for-user
Collaborator
|
@kabakaev as you can see, the conflicts I had to fix resulted in taking the path to a new docs PR. I'll update the code PR to reflect that and your attribution will remain in this new docs PR. I will close this in favor of the new #2590 which will be waiting only on the code PR fluent/fluent-bit#3191 merging. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
This PR can be merged only if the FLB PR 3191 is accepted and merged.