DE14689 add support to reconnect kafka cluster admin #187
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.
fix DE14689 sarama cluster admin lost kafka connection after 10 min.
kafka.metadata.refresh-frequency: 300s
for sarama kafka client's built inbackgroundMetadataUpdater
task (client.conf.Metadata.RefreshFrequency
) as mentioned in: producer write broken pipe IBM/sarama#1565backgroundMetadataUpdater
task cannot keep the kafka connection alive for ClusterAdmin(ClusterAdmin uses different broker connection from the ones used inbackgroundMetadataUpdater
). As a workaroundReloadClusterAdmin
has been added so service can recreate ClusterAdmin instance when the connection is broken/lost.CloseProducer
to close dynamic producers created in webhook service to reduce resource usage.