[
https://issues.apache.org/jira/browse/BEAM-8382?focusedWorklogId=388125&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388125
]
ASF GitHub Bot logged work on BEAM-8382:
----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/20 19:53
Start Date: 16/Feb/20 19:53
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-586745248
Hi, @aromanenko-dev I have already removed the BackoffRateLimiter from this
PR, and I would like to finish the unit tests and documentation for
FixedDelayRateLimiter and narrow the scope of the PR back to that since it's a
variant of what we're currently using in production. Is there any chance we can
get that in? It would be good to know before I put in the remaining work. I
think the custom rate limit policy is a nice to have so I can leave that in if
you want in case anyone wants to implement their own adaptive rate limit policy
in the future. It would also provide a way to change the fixed delay interval
of a running pipeline since that was another use case you were interested in.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 388125)
Time Spent: 12h 40m (was: 12.5h)
> 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: 12h 40m
> 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)
