You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by GitBox <gi...@apache.org> on 2020/02/27 16:53:26 UTC
[GitHub] [beam] aromanenko-dev edited a comment on issue #10973: KinesisIO
retry LimitExceededException
aromanenko-dev edited a comment on issue #10973: KinesisIO retry LimitExceededException
URL: https://github.com/apache/beam/pull/10973#issuecomment-592051559
@ameihm0912 Yes, I see your point and this is actually a different but similar issue imo.
One of the option to overcome this could be using internal AWS `RetryPolicy` as I showed in [this comment](https://github.com/apache/beam/pull/9765#issuecomment-562136257) - in this case you just need to create new `AWSClientsProvider`, based on current `BasicKinesisProvider`, and override the method `getKinesisClient()` with configured custom `RetryPolicy` and `BackoffStrategy`. Then set this new `AWSClientsProvider` by `withAWSClientsProvider(AWSClientsProvider)`. Though, be aware that this policy will be applied to all other `AmazonKinesis ` requests as well afaik.
Another option can using Beam `FluentBackoff`class as many other Beam IOs do, like `ClickHouseIO` for example.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services