[
https://issues.apache.org/jira/browse/BEAM-8382?focusedWorklogId=332066&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-332066
]
ASF GitHub Bot logged work on BEAM-8382:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Oct/19 16:21
Start Date: 22/Oct/19 16:21
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #9765: [BEAM-8382]
Add polling interval to KinesisIO.Read
URL: https://github.com/apache/beam/pull/9765#issuecomment-545042188
@cmachgodaddy I think @jfarr is right - in simple case all shards are
discovered by `DynamicCheckpointGenerator` and put into the list of
`KinesisSource`s during `split()` executing on driver. Every `KinesisSource`
may contain more than 1 shard (see `KinesisReaderCheckpoint`) in case if number
of workers is less the total number of shards but it's not possible that 2
different sources had reference to the same shard. Then, all these split
sources will be distributed over workers by your resource manager. So, every
Source will be responsible for one or more different shards and it will spawn
one thread per shard in `ShardReadersPool`.
----------------------------------------------------------------
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: 332066)
Time Spent: 4h 40m (was: 4.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: 4h 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)
