[
https://issues.apache.org/jira/browse/FLINK-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20465:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Fail globally when not resuming from the latest checkpoint in regional
> failover
> -------------------------------------------------------------------------------
>
> Key: FLINK-20465
> URL: https://issues.apache.org/jira/browse/FLINK-20465
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Till Rohrmann
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> As a follow up for FLINK-20290 we should assert that we resume from the
> latest checkpoint when doing a regional failover in the
> {{SourceCoordinators}} in order to avoid losing input splits (see
> FLINK-20427). If the assumption does not hold, then we should fail the job
> globally so that we reset the master state to a consistent view of the state.
> Such a behaviour can act as a safety net in case that Flink ever tries to
> recover from not the latest available checkpoint.
> One idea how to solve it is to remember the latest completed checkpoint id
> somewhere along the way to the
> {{SplitAssignmentTracker.getAndRemoveUncheckpointedAssignment}} and failing
> when the restored checkpoint id is smaller.
> cc [~sewen], [~jqin]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
