[jira] [Work logged] (BEAM-8382) Add polling interval to KinesisIO.Read

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 03/Nov/19 11:04
            Start Date: 03/Nov/19 11:04
    Worklog Time Spent: 10m 
      Work Description: jfarr commented on issue #9765: [WIP][BEAM-8382] Add rate limit policy to KinesisIO.Read
URL: https://github.com/apache/beam/pull/9765#issuecomment-549125609
 
 
   Hi @aromanenko-dev, I replaced the polling interval with a rate limit policy configured with the following methods:
   
   `withBackoffRateLimitPolicy(FluentBackoff fluentBackoff)`
   Specifies the rate limit policy as BackoffRateLimiter.
   
   `withFixedDelayRateLimitPolicy()`
   Specifies the rate limit policy as FixedDelayRateLimiter with the default delay of 1 second.
   
   `withFixedDelayRateLimitPolicy(Duration delay)`
   Specifies the rate limit policy as FixedDelayRateLimiter with the given delay.
   
   `withCustomRateLimitPolicy(RateLimitPolicyFactory rateLimitPolicyFactory)`
   Specifies the RateLimitPolicyFactory for a custom rate limiter.
   
   The default is a no limiter policy that preserves the behavior of the current implementation.
   
   wdyt?
 
----------------------------------------------------------------
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


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

    Worklog Id:     (was: 337816)
    Time Spent: 5.5h  (was: 5h 20m)

> Add polling interval to KinesisIO.Read
> --------------------------------------
>
>                 Key: BEAM-8382
>                 URL: https://issues.apache.org/jira/browse/BEAM-8382
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-kinesis
>    Affects Versions: 2.13.0, 2.14.0, 2.15.0
>            Reporter: Jonothan Farr
>            Assignee: Jonothan Farr
>            Priority: Major
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> With the current implementation we are observing Kinesis throttling due to ReadProvisionedThroughputExceeded on the order of hundreds of times per second, regardless of the actual Kinesis throughput. This is because the ShardReadersPool readLoop() method is polling getRecords() as fast as possible.
> From the KDS documentation:
> {quote}Each shard can support up to five read transactions per second.
> {quote}
> and
> {quote}For best results, sleep for at least 1 second (1,000 milliseconds) between calls to getRecords to avoid exceeding the limit on getRecords frequency.
> {quote}
> [https://docs.aws.amazon.com/streams/latest/dev/service-sizes-and-limits.html]
> [https://docs.aws.amazon.com/streams/latest/dev/developing-consumers-with-sdk.html]



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