[
https://issues.apache.org/jira/browse/FLINK-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951717#comment-16951717
]
Robert Metzger commented on FLINK-14175:
----------------------------------------
I would target {{master}} for the upcoming 1.10 release (and maybe to the
{{release-1.9}} branch for the next 1.9.x release)
For backporting FLINK-12847, to older versions: For bugfix releases, we usually
only upgrade dependency versions for severe bugs or security issues.
Since connectors are only distributed via maven repositories, you could
consider backporting the version change yourself, and then releasing the
connector under a different name to maven central?
> 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
>
> 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)
