{{ message }}
Repository navigation
Fixed - RReliableTopic renewal and status update retry handling #7391 - #7394
Open
ronitgupta138 wants to merge 1 commit into
Open
ronitgupta138 wants to merge 1 commit into
ronitgupta138 wants to merge 1 commit into
Conversation
…son#7391 Signed-off-by: Ronit Gupta <ronitgupta138@gmail.com>
ronitgupta138
force-pushed
the
fix/reliable-topic-renewal-retry
branch
from
October 17, 2026 06:25
7d0c01c to
0810d4f
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Fixes #7391
When Redis rejects writes transiently (e.g. during replica resynchronization with NOREPLICAS, failover, or ACL updates):
renewExpiration(), if the renewal execution future failed with an error, it was never rescheduled. OncereliableTopicWatchdogTimeoutelapsed, the subscriber score expired.updateFuturefailed,poll(id)was not rescheduled, permanently halting message consumption for active subscribers.tostring(), causing Redis stream ID parsing errors (ERR Invalid stream ID specified as stream command argument) when consumer groups are destroyed.This change:
renewExpiration()when renewal fails andsubscribed.get() == true.poll(id)with backoff whenupdateFutureencounters a transient failure while still subscribed.string.format('%.0f', score).