[
https://issues.apache.org/jira/browse/FLINK-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957197#comment-16957197
]
Thomas Weise commented on FLINK-14175:
--------------------------------------
Given the nature of the issue I think it would be justifiable to backport just
the version change to 1.9.x and possibly 1.8.x (if possible). That would ensure
that users building the connector don't run into the bug. Backporting entire
FLINK-12847 is not appropriate for a patch release.
> Upgrade KPL version in flink-connector-kinesis to fix application OOM
> ---------------------------------------------------------------------
>
> Key: FLINK-14175
> URL: https://issues.apache.org/jira/browse/FLINK-14175
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Affects Versions: 1.6.3, 1.6.4, 1.6.5, 1.7.2, 1.7.3, 1.8.0, 1.8.1, 1.8.2,
> 1.9.0
> Environment: [link title|http://example.com][link
> title|http://example.com]
> Reporter: Abhilasha Seth
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The [KPL
> version|https://github.com/apache/flink/blob/release-1.9/flink-connectors/flink-connector-kinesis/pom.xml#L38]
> (0.12.9) used by flink-connector-kinesis in the affected Flink versions has
> a thread leak bug that causes applications to run out of memory after
> frequent restarts:
> KPL Issue - [https://github.com/awslabs/amazon-kinesis-producer/issues/224]
> Fix - [https://github.com/awslabs/amazon-kinesis-producer/pull/225/files]
> Upgrading KPL to 0.12.10 or higher is necessary to avoid this issue. The
> recommended version to upgrade would be the latest (0.13.1)
> Note that KPL version in Flink 1.10.0 has been updated to the latest version
> (0.13.1): https://issues.apache.org/jira/browse/FLINK-12847
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
