You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/07/08 22:38:01 UTC
[jira] [Updated] (FLINK-18112) Approximate Task-Local Recovery --
Milestone One
[ https://issues.apache.org/jira/browse/FLINK-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-18112:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> Approximate Task-Local Recovery -- Milestone One
> ------------------------------------------------
>
> Key: FLINK-18112
> URL: https://issues.apache.org/jira/browse/FLINK-18112
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Checkpointing, Runtime / Coordination, Runtime / Network
> Affects Versions: 1.12.0
> Reporter: Yuan Mei
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> This is the Jira ticket for Milestone One of [FLIP-135 Approximate Task-Local Recovery|https://cwiki.apache.org/confluence/display/FLINK/FLIP-135+Approximate+Task-Local+Recovery]
> In short, in Approximate Task-Local Recovery, if a task fails, only the failed task restarts without affecting the rest of the job. To ease discussion, we divide the problem of approximate task-local recovery into three parts with each part only focusing on addressing a set of problems. This Jira ticket focuses on address the first milestone.
> Milestone One: sink recovery. Here a sink task stands for no consumers reading data from it. In this scenario, if a sink vertex fails, the sink is restarted from the last successfully completed checkpoint and data loss is expected. If a non-sink vertex fails, a regional failover strategy takes place. In milestone one, we focus on issues related to task failure handling and upstream reconnection.
>
> Milestone one includes two parts of change:
> *Part 1*: Network Part: how the failed task able to link to the upstream Result(Sub)Partitions, and continue processing data
> *Part 2*: Scheduling part, a new failover strategy to restart the sink only when the sink fails.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)