[
https://issues.apache.org/jira/browse/FLINK-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166183#comment-16166183
]
Tzu-Li (Gordon) Tai commented on FLINK-7622:
--------------------------------------------
[~phoenixjiangnan] curious about how this ticket would relate to FLINK-7508.
Does switching the KPL producer to thread-pool mode also indirectly solve this
issue? Ideally, after switching to thread-pool mode, the producer should block
operations of adding new records to KPL when the thread-pool has no capacity.
> 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: Kinesis Connector
> Reporter: Tzu-Li (Gordon) Tai
>
> 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
(v6.4.14#64029)
