Fix pattern consumer fails when a subscribed topic is deleted #319
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
When a topic that a pattern consumer is subscribed to is deleted, the consumer's sub-consumer tries to reconnect. However, it encounters a "topic not found" error. Currently, this error causes all pending waiters to fail, leading to an
AlreadyClosedException
whenconsumer.ReceiveAsync()
is called. This issue can disrupt other consumers.To fix this, if a sub-consumer encounters a "topic not found" error during reconnection, we should simply remove that consumer from the pattern consumer instead of throwing an exception.
Modification