[
https://issues.apache.org/jira/browse/CAMEL-19582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747449#comment-17747449
]
Hamed Hatami edited comment on CAMEL-19582 at 7/26/23 10:37 AM:
----------------------------------------------------------------
[~davsclaus]
I'm not sure if that's a good way to fulfill this requirement cause the health
checks always are used from higher layer of the component whereas we tend to
have such a feature within the component means when there a break-down then
another connection needs to be taken immediately without extra efforts for
upper layer.
was (Author: JIRAUSER301224):
I'm not sure if that's a good way to fulfill this requirement cause the health
checks always are used from higher layer of the component whereas we tend to
have such a feature within the component means when there a break-down then
another connection needs to be taken immediately without extra efforts for
upper layer.
> Lack of Camel aws2 Kinesis Fault-Tolerance
> ------------------------------------------
>
> Key: CAMEL-19582
> URL: https://issues.apache.org/jira/browse/CAMEL-19582
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
> Affects Versions: 4.0-M3
> Reporter: Hamed Hatami
> Priority: Major
>
> In "aws2-kinesis" component , there's no retry mechanism (resiliency is not
> considered) just in case there's any connectivity outage, therefore if
> Kinesis goes off , Kinesis Client won't get back to work anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
