[ 
https://issues.apache.org/jira/browse/BEAM-9476?focusedWorklogId=400402&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-400402
 ]

ASF GitHub Bot logged work on BEAM-9476:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Mar/20 22:19
            Start Date: 09/Mar/20 22:19
    Worklog Time Spent: 10m 
      Work Description: ameihm0912 commented on issue #10973: [BEAM-9476] 
KinesisIO retry LimitExceededException
URL: https://github.com/apache/beam/pull/10973#issuecomment-596806642
 
 
   @aromanenko-dev updated to use `FluentBackoff` and references to Jira issue 
added
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 400402)
    Remaining Estimate: 0h
            Time Spent: 10m

> KinesisIO DescribeStream transient errors are not retried
> ---------------------------------------------------------
>
>                 Key: BEAM-9476
>                 URL: https://issues.apache.org/jira/browse/BEAM-9476
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-kinesis
>            Reporter: Aaron Meihm
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> During Kinesis stream setup {{DescribeStream}} is used in {{listShards}}. 
> This API call has quota limits that can become problematic when attempting to 
> configure multiple Kinesis streams in the same AWS account. AWS currently 
> limits this call by default to 10 times per second for a given account. With 
> multiple streams, this can be hit and results in a {{RuntimeException}} being 
> thrown immediately upon the first error.
> Ideally the rate limited call can be retried a number of times before giving 
> up instead of failing immediately.
> I have a work in progress PR that resolves this issue at 
> https://github.com/apache/beam/pull/10973.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to