Fix ssl timeout errors for Quix applications #254
Merged
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.
Problem
Applications created via
Application.Quix()
log timeout errors after becoming idle for some time.Example:
Looks like it's a known issue - confluentinc/librdkafka#3109.
Solution
Set default values for
connections.max.idle.ms
andmetadata.max.age.ms
to 3min.It makes librdkafka close idle connections before the LB does it and updates broker metadata more often.
These values are set by
QuixKafkaConfigsBuilder
and only for the Quix apps.They can be overwritten by passing
extra_consumer_config
andextra_producer_config
toApplication.Quix
.