Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Flink supports stopping with savepoint as documented here:
Stopping with savepoint will invoke these 3 interface functions Flink functions.
- cancel()
- snapshotState()
- close()
However, the current implementation of stopping with savepoint will cause an issuedInstant to be null when snapshotState is invoked. This is so as cancel() will set the issuedInstant to null, causing the snapshotState() to add a null value to the LinkState list.
As such, when resuming from a savepoint, there will be:
- data loss if the LATEST (by not specifying a value for, i.e. default value) read.start.commit is used
- duplicated data if the EARLIEST read.start.commit is used
Attachments
Issue Links
- links to