[
https://issues.apache.org/jira/browse/FLINK-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328723#comment-17328723
]
Flink Jira Bot commented on FLINK-7622:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Respect local KPL queue size in FlinkKinesisProducer when adding records to
> KPL client
> --------------------------------------------------------------------------------------
>
> Key: FLINK-7622
> URL: https://issues.apache.org/jira/browse/FLINK-7622
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Major
> Labels: stale-major
>
> This issue was brought to discussion by [~sthm] offline.
> Currently, records are added to the Kinesis KPL producer client without
> checking the number of outstanding records within the local KPL queue. This
> manner is basically neglecting backpressure when producing to Kinesis through
> KPL, and can therefore exhaust system resources.
> We should respect {{producer.getOutstandingRecordsCount()}} as a measure of
> backpressure, and propagate backpressure upstream by blocking further sink
> invocations when some threshold of outstanding record count is exceeded. The
> recommended threshold [1] seems to be 10,000.
> [1]
> https://aws.amazon.com/blogs/big-data/implementing-efficient-and-reliable-producers-with-the-amazon-kinesis-producer-library/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
