This repository has been archived by the owner on Mar 17, 2024. It is now read-only.
Implement connection pooling for redis lookup #459
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The Redis Lookup table implementation was not thread safe, so the exporter is failing when having more than one cluster.
This PR implement the redis connection pool, following documentation from
debasishg/scala-redis: https://github.com/debasishg/scala-redis#using-client-poolingDocker image built from that PR is available here: https://hub.docker.com/layers/guillaumeroland/kafka-lag-exporter/0.8.3-SNAPSHOT/images/sha256-856f2aeee34270d3f0793157e9fff196f397ee91c3ad8f3de5573e5590102c69?context=explore
I also made some changes in the docker-compose.yml file to make local development easier, as previous images were not compatible with Apple ARM-based CPUs.