Zakelly Lan created FLINK-34189:
-----------------------------------
Summary: FLIP-416: Deprecate and remove the RestoreMode#LEGACY
Key: FLINK-34189
URL: https://issues.apache.org/jira/browse/FLINK-34189
Project: Flink
Issue Type: Improvement
Components: Runtime / Checkpointing
Reporter: Zakelly Lan
Assignee: Zakelly Lan
Fix For: 2.0.0, 1.19.0
[https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=287607202]
The [FLIP-193|https://cwiki.apache.org/confluence/x/bIyqCw] introduced two
modes of state file ownership during checkpoint restoration: RestoreMode#CLAIM
and RestoreMode#NO_CLAIM. The LEGACY mode, which was how Flink worked until
1.15, has been superseded by NO_CLAIM as the default mode. The main drawback of
LEGACY mode is that the new job relies on artifacts from the old job without
cleaning them up, leaving users uncertain about when it is safe to delete the
old checkpoint directories. This leads to the accumulation of unnecessary
checkpoint files that are never cleaned up. Considering cluster availability
and job maintenance, it is not recommended to use LEGACY mode. Users could
choose the other two modes to get a clear semantic for the state file ownership.
This FLIP proposes to deprecate the LEGACY mode and remove it completely in the
upcoming Flink 2.0. This will make the semantic clear as well as eliminate many
bugs caused by mode transitions involving LEGACY mode (e.g.
!https://issues.apache.org/jira/secure/viewavatar?size=xsmall&avatarId=21133&avatarType=issuetype!
FLINK-27114 - On JM restart, the information about the initial checkpoints can
be lost OPEN ) and enhance code maintainability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
