This repository was archived by the owner on Jan 4, 2026. It is now read-only.
fix: improve service discovery to use redis hashes#12
Merged
Conversation
ItsKev
force-pushed
the
fix/service-discovery
branch
from
204f408 to
6669447
Compare
ItsKev
force-pushed
the
fix/service-discovery
branch
from
6669447 to
c3fa704
Compare
lusu007
approved these changes
Jan 2, 2026
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Pull Request
Description
Service Discovery now uses Redis Hashes to remove the need for the rather complex SCAN logic as we had timeouts or missing entries multiple times.
Type of Change
Testing
Checklist