[FLINK-29324] Calling Kinesis connector close method before subtask starts running results in NPE

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.14.5, 1.15.2
• Fix Version/s: 1.16.0, 1.17.0, 1.15.3
• Component/s: Connectors / Kinesis
• Labels: pull-request-available
• Assignee: Dongming.Hu
• Reporter: Anthony Pounds-Cornish
• Created: 16/Sep/22 11:30
• Updated: 28/Nov/22 11:04
• Resolved: 20/Sep/22 15:52

Description

When a Flink application is stopped before a Kinesis connector subtask has been started, the following exception is thrown:

java.lang.NullPointerException
at org.apache.flink.streaming.connectors.kinesis.FlinkKinesisConsumer.close(FlinkKinesisConsumer.java:421)
...

This appears to be related to the fact that fetcher creation may not occur by the time it is referenced when the consumer is closed.

A suggested fix is to make the close() method null safe as it has been in the cancel() method.

Issue Links

• is related to: FLINK-30224 Add IT Case for NPE in FlinkKinesisConsumer's close() method
• links to: GitHub Pull Request #20853