[
https://issues.apache.org/jira/browse/FLINK-18112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18112:
-----------------------------------
Labels: stale-assigned (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it. If the "warning_label" label is not removed in 7 days, the
issue will be automatically unassigned.
> 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
> Assignee: Yuan Mei
> Priority: Major
> Labels: stale-assigned
>
> 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)
