[
https://issues.apache.org/jira/browse/FLINK-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hong Liang Teoh updated FLINK-10536:
------------------------------------
Fix Version/s: aws-connector-5.1.0
> Flink Kinesis Consumer leading to job failure due to
> ProvisionedThroughputExceededException
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-10536
> URL: https://issues.apache.org/jira/browse/FLINK-10536
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Affects Versions: 1.5.2
> Reporter: Ravi Bhushan Ratnakar
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
> Fix For: aws-connector-5.1.0
>
>
> *Background:*
> Flink Kinesis consumer, while consuming message from a shard, it retries for
> a configured number of attempts and then after it throws
> "ProvisionedThroughputExceededException" and which bubbles up to top level
> and eventually which leads to failure of the running streaming job.
> *Improvement:*
> In some scenario it may be desirable that to skip some of the records by
> skipping that "shardIterator" and move to next iterator in "ShardConsumer"
> and log this as metrics. This can be configurable through some property. This
> way those application which can tolerate to skip some messages can continue
> to keep running.
>
> If this idea seems useful, i would like to contribute on this. Please let me
> know the process
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
