[
https://issues.apache.org/jira/browse/FLINK-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10536:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> *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.1#820001)
