[
https://issues.apache.org/jira/browse/FLINK-23528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496581#comment-17496581
]
Danny Cranmer commented on FLINK-23528:
---------------------------------------
[~arvid] any update on this? I have removed the 1.15 fix version, feel free to
revert if this is on target
> 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.15.0, 1.14.3
> Reporter: Piotr Nowojski
> Assignee: Arvid Heise
> Priority: Critical
> Labels: pull-request-available, stale-assigned
> Fix For: 1.16.0
>
>
> {{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.1#820001)
