flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8360) Implement task-local state recovery
Date Thu, 11 Jan 2018 14:26:03 GMT

    [ https://issues.apache.org/jira/browse/FLINK-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322290#comment-16322290

ASF GitHub Bot commented on FLINK-8360:

Github user pnowojski commented on a diff in the pull request:

    --- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/state/StateUtil.java ---
    @@ -71,4 +72,22 @@ public static void discardStateFuture(RunnableFuture<? extends StateObject>
    +	/**
    +	 * Discards the given state collection future by first trying to cancel it. If this
is not possible, then
    +	 * the state object contained in the future is calculated and afterwards discarded.
    +	 *
    +	 * @param stateCollectionFuture to be discarded
    +	 * @throws Exception if the discard operation failed
    +	 */
    +	public static void discardStateCollectionFuture(
    --- End diff --
    It seems like a dead code both in this commit and it the whole PR. Isn't it?

> Implement task-local state recovery
> -----------------------------------
>                 Key: FLINK-8360
>                 URL: https://issues.apache.org/jira/browse/FLINK-8360
>             Project: Flink
>          Issue Type: New Feature
>          Components: State Backends, Checkpointing
>            Reporter: Stefan Richter
>            Assignee: Stefan Richter
>             Fix For: 1.5.0
> This issue tracks the development of recovery from task-local state. The main idea is
to have a secondary, local copy of the checkpointed state, while there is still a primary
copy in DFS that we report to the checkpoint coordinator.
> Recovery can attempt to restore from the secondary local copy, if available, to save
network bandwidth. This requires that the assignment from tasks to slots is as sticky is possible.
> For starters, we will implement this feature for all managed keyed states and can easily
enhance it to all other state types (e.g. operator state) later.

This message was sent by Atlassian JIRA

View raw message