[fix] [client] Messages lost due to TopicListWatcher reconnect #21852
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.
Motivation
Issue
public/default/*public/default/tp-1Root cause
Case-1:
start consumercreate topicTopicListWatcherTopicListWatcherregistered, the consumer will not receive any messages from the new topicCase-2:
TopicListWatcher reconnectcreate topicTopicListWatcherreconnectedThis issue only affects the releases
>=3.1, because before3.1there is a supplementary mechanismscheduled recheckPatternTimeout, it makes the issues will not occur. This supplementary mechanism was removed at3.1, see #20779Modifications
TopicListWatcherreconnected, re-check the topics list.Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository: x