[FLINK-23528] stop-with-savepoint can fail with FlinkKinesisConsumer

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.11.3, 1.13.1, 1.12.4, 1.14.3, 1.15.1
• Fix Version/s: 1.16.0, 1.15.2
• Component/s: Connectors / Kinesis
• Labels: pull-request-available stale-assigned
• Assignee: Krzysztof Dziolak
• Reporter: Piotr Nowojski
• Created: 28/Jul/21 10:28
• Updated: 10/Jul/24 07:43
• Resolved: 25/Jul/22 09:01

Description

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.

Issue Links

• duplicates: FLINK-29015 Flink stop with/without savepoint does not work with kinesis consumer
• is duplicated by: FLINK-23538 FlinkKinesisConsumer should not interrupt the legacy source thread in cancel
• is related to: FLINK-21028 Streaming application didn't stop properly
• relates to: FLINK-31183 Flink Kinesis EFO Consumer can fail to stop gracefully
• relates to: FLINK-23527 Clarify `SourceFunction#cancel()` contract about interrupting
• links to: GitHub Pull Request #16882
• links to: GitHub Pull Request #17189
• links to: GitHub Pull Request #20133