Skip to content
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

output: Limit max duration of outgoing connection to help load balancing #6

Closed
jiping-s opened this issue Jun 3, 2021 · 0 comments · Fixed by #15
Closed

output: Limit max duration of outgoing connection to help load balancing #6

jiping-s opened this issue Jun 3, 2021 · 0 comments · Fixed by #15
Labels
enhancement New feature or request

Comments

@jiping-s
Copy link
Collaborator

jiping-s commented Jun 3, 2021

Background

The outgoing connections from fluentd forward client have been designed to be persistent, unlike the async request approach used in fluent-bit with pooling. It works fine except it's very poor for load balancing on the server side, as connections stick to the same server node forever until either side is restarted.

What to do

Automatically close the connections after certain duration of time (e.g. 30m) should be able to address this, and also avoid pausing before next connection attempt in such situations.

Note a connection shouldn't be closed if there are still pending acknowledgements, which could be a problem if traffic never stops (need better ideas). Meanwhile a new connection cannot be opened until the old one is closed (current behavior), or the order of logs cannot be guaranteed.

@jiping-s jiping-s added the enhancement New feature or request label Jun 3, 2021
@jiping-s jiping-s changed the title output: limit max duration of outgoing connection to help load balancing output: Limit max duration of outgoing connection to help load balancing Jun 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant