fix(adapter): add retry logic for redis psubscribe timeout #569
+336
−11
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
In distributed environments, the Redis handshake can fail due to temporary network timeouts, causing the adapter to crash on initialization.
Solution
Implemented a retry mechanism with exponential backoff for the
psubscribecall (andpSubscribefor Redis v4).Changes
withRetryhelper method and wrapped subscription logic.test/**/*and enabledesModuleInteropfor testing compatibility.Verification
Tests pass locally:
✔ should retry psubscribe call✔ should retry pSubscribe call (Redis v4)