Log exceptions for dynamically added streams with misaligned regions, rather than allowing them to propagate #1326
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
… propagating exception
furq-aws
force-pushed
the
region-mismatch-graceful-failure
branch
from
b16d99b
to
a348a35
Compare
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.
Issue #, if available:
N/A.
Description of changes:
When dynamically adding a stream to an application at runtime with a region that does not align with that of the Kinesis client, log the exception and emit a metric, instead of allowing the exception to propagate and bypass stream syncing logic.
Streams with mismatching regions specified during the construction of the
Schedulerwill continue to fast-fail.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.