[
https://issues.apache.org/jira/browse/FLINK-23528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570785#comment-17570785
]
Danny Cranmer commented on FLINK-23528:
---------------------------------------
Merged:
- 1.15.x:
[7cd5fe9|https://github.com/apache/flink/commit/7cd5fe93035c5d875d10d9f3cb1d84d4ed045dc0]
- master:
[4bbf319|https://github.com/apache/flink/commit/4bbf3194dc3816dcaa6a76ed7adf0fd228b16293]
> stop-with-savepoint can fail with FlinkKinesisConsumer
> ------------------------------------------------------
>
> Key: FLINK-23528
> URL: https://issues.apache.org/jira/browse/FLINK-23528
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Affects Versions: 1.11.3, 1.13.1, 1.12.4, 1.14.3, 1.15.1
> Reporter: Piotr Nowojski
> Assignee: Krzysztof Dziolak
> Priority: Critical
> Labels: pull-request-available, stale-assigned
> Fix For: 1.16.0, 1.15.2
>
>
> {{FlinkKinesisConsumer#cancel()}} (inside
> {{KinesisDataFetcher#shutdownFetcher()}}) shouldn't be interrupting source
> thread. Otherwise, as described in FLINK-23527, network stack can be left in
> an invalid state and downstream tasks can encounter deserialisation errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
