Recreate AEH Processor in the event of an error before retrying the processing operation #3614
+47
−46
Conversation
This file contains 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
Recreate AEH Processor in the event of an error before retrying the processing operation Signed-off-by: MattCosturos <48531957+MattCosturos@users.noreply.github.com>
|
See failing build tests |
|
Updated to log the initial connection error, and then retry after 5 seconds. Same way we handle errors after the initial creation. |
…processing events in Azure Event Hubs subscription. Signed-off-by: Matt Costuros <mcosturos@moog.com>
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.
Recreate AEH Processor in the event of an error before retrying the processing operation
Description
Moved the creation and setup of the Azure Event Hub Processor inside the main loop.
The processor.run only returns a non-recoverable error. Therefore we must re-create new processor and setup the subscription.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #3573
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: