[
https://issues.apache.org/jira/browse/FLINK-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bowen Li updated FLINK-7367:
----------------------------
Description:
Right now, FlinkKinesisProducer only expose two configs for the underlying
KinesisProducer:
- AGGREGATION_MAX_COUNT
- COLLECTION_MAX_COUNT
Well, according to [AWS
doc|http://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-config.html] and
[their sample on
github|https://github.com/awslabs/amazon-kinesis-producer/blob/master/java/amazon-kinesis-producer-sample/default_config.properties],
developers can set more to make the max use of KinesisProducer, and make it
fault-tolerant (e.g. by increasing timeout).
I select a few more configs that we need when using Flink with Kinesis:
- MAX_CONNECTIONS
- RATE_LIMIT
- RECORD_MAX_BUFFERED_TIME
- RECORD_TIME_TO_LIVE
- REQUEST_TIMEOUT
Flink is using KPL's default values. They make Flink writing too fast to
Kinesis, which fail Flink job too frequently. We need to parameterize
FlinkKinesisProducer to pass in the above params, in order to slowing down
Flink's write rate to Kinesis.
was:
Right now, FlinkKinesisProducer only expose two configs for the underlying
KinesisProducer:
- AGGREGATION_MAX_COUNT
- COLLECTION_MAX_COUNT
Well, according to [AWS
doc|http://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-config.html] and
[their sample on
github|https://github.com/awslabs/amazon-kinesis-producer/blob/master/java/amazon-kinesis-producer-sample/default_config.properties],
developers can set more to make the max use of KinesisProducer, and make it
fault-tolerant (e.g. by increasing timeout).
I select a few more configs that we need when using Flink with Kinesis:
- MAX_CONNECTIONS
- RATE_LIMIT
- RECORD_MAX_BUFFERED_TIME
- RECORD_TIME_TO_LIVE
- REQUEST_TIMEOUT
We need to parameterize FlinkKinesisProducer to pass in the above params, in
order to cater to our need
> Parameterize more configs for FlinkKinesisProducer (RecordMaxBufferedTime,
> MaxConnections, RequestTimeout, etc)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-7367
> URL: https://issues.apache.org/jira/browse/FLINK-7367
> Project: Flink
> Issue Type: Bug
> Components: Kinesis Connector
> Affects Versions: 1.3.0
> Reporter: Bowen Li
> Assignee: Bowen Li
> Fix For: 1.4.0, 1.3.3
>
>
> Right now, FlinkKinesisProducer only expose two configs for the underlying
> KinesisProducer:
> - AGGREGATION_MAX_COUNT
> - COLLECTION_MAX_COUNT
> Well, according to [AWS
> doc|http://docs.aws.amazon.com/streams/latest/dev/kinesis-kpl-config.html]
> and [their sample on
> github|https://github.com/awslabs/amazon-kinesis-producer/blob/master/java/amazon-kinesis-producer-sample/default_config.properties],
> developers can set more to make the max use of KinesisProducer, and make it
> fault-tolerant (e.g. by increasing timeout).
> I select a few more configs that we need when using Flink with Kinesis:
> - MAX_CONNECTIONS
> - RATE_LIMIT
> - RECORD_MAX_BUFFERED_TIME
> - RECORD_TIME_TO_LIVE
> - REQUEST_TIMEOUT
> Flink is using KPL's default values. They make Flink writing too fast to
> Kinesis, which fail Flink job too frequently. We need to parameterize
> FlinkKinesisProducer to pass in the above params, in order to slowing down
> Flink's write rate to Kinesis.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
