[
https://issues.apache.org/jira/browse/FLINK-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski closed FLINK-24344.
----------------------------------
Fix Version/s: (was: 1.14.0)
1.14.1
Resolution: Fixed
Merged to master as 815191a6f5e^, 815191a6f5e
Merged to release-1.14 as 464849d74bd^ and 464849d74bd
> Handling of IOExceptions when triggering checkpoints doesn't cause job
> failover
> -------------------------------------------------------------------------------
>
> Key: FLINK-24344
> URL: https://issues.apache.org/jira/browse/FLINK-24344
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.14.0
> Reporter: Piotr Nowojski
> Assignee: Anton Kalashnikov
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.15.0, 1.14.1
>
>
> When running
> {{CheckpointCoordinatorTest#testTriggerCheckpointAfterIOException}}, it
> simulates an {{IOException}} thrown from
> {{CheckpointCoordinator#initializeCheckpoint}}. Which makes sense but:
> # This exception never reaches {{CheckpointFailureManager}} because of the
> logic in {{CheckpointCoordinator#onTriggerFailure()}}. So the main purpose of
> the FLINK-23189 ticket is not working as intended.
> # it would be however much much better to throw {{IOException}} from
> {{checkpointStorageView.initializeLocationForCheckpoint}} rather from
> {{checkpointIdCounter.getAndIncrement}}. The latter could be refactored out,
> while the production {{IOException}} can be thrown in reality from
> {{initializeLocationForCheckpoint}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
