fluentd exporter: Disconnect and retry DNS lookup on socket failure #469
Conversation
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
|
any test cases in your PR? It would be better that your changed could be covered by unit test. |
|
@lalitb any comment on this? |
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.
On socket failure, re-initialize the address info.
Along with #468, this triggers a new DNS lookup.
To prevent immediate retries that quickly exhaust the retry count,
add a retry_delay_ms to FluentdExporterOptions, defaulting to 1000ms.
We found this useful when deploying in a Kubernetes environment,
where the targeted service endpoint may not yet be up when a logging client starts up.