Fix: Broker Reconnection Persistent Failure Event Handling #5267
Conversation
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
…n on authentication errors This commit introduces a mechanism to track persistent broker reconnection failures and report them to the application if a specified threshold is reached. It also forces DNS re-resolution on authentication failures to handle scenarios where broker IPs may change after restarts. Additionally, new configuration options and error codes are added to support these features.
…istent failure tracking This commit introduces the `reconnect.failure.report.ms` configuration option, which allows applications to receive notifications of persistent broker reconnection failures after a specified duration. It includes unit tests to validate the functionality of persistent failure tracking, ensuring correct behavior for failure detection, reporting, and configuration validation. Additionally, a new integration test is added to verify the error handling when brokers are unreachable for extended periods.
|
🎉 All Contributor License Agreements have been signed. Ready to merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 request introduces a mechanism to track persistent broker reconnection failures and report them to the application if a specified threshold is reached. It also forces DNS re-resolution on authentication failures to handle scenarios where broker IPs may change after restarts. Additionally, new configuration options and error codes are added to support these features.
It also includes unit tests to validate the functionality of persistent failure tracking, ensuring correct behavior for failure detection, reporting, and configuration validation. Additionally, a new integration test is added to verify the error handling when brokers are unreachable for extended periods.
New configuration added -
reconnect.failure.report.ms, which allows applications to receive notifications of persistent broker reconnection failures after a specified duration.