Resilient stream example with connection retry #810
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.
This change resolves issue #809
This revised example demonstrates a robust streaming consumer that does not panic on the first transient network error (e.g., BrokerTransportFailure on IPv6 ::1 for localhost). Instead, it restarts the stream with an exponential backoff, allowing librdkafka to retry and fall back to alternative broker addresses (such as 127.0.0.1) when available. The processing of messages remains asynchronous via
tokio::spawn, while the outer loop handles stream errors gracefully and continuously attempts to reconnect.