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

ASF GitHub Bot commented on FLINK-8360:
---------------------------------------

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

    https://github.com/apache/flink/pull/5239#discussion_r168472392
  
    --- Diff: 
flink-runtime/src/main/java/org/apache/flink/runtime/state/heap/HeapKeyedStateBackend.java
 ---
    @@ -507,17 +509,78 @@ public boolean supportsAsynchronousSnapshots() {
                return localRecoveryConfig;
        }
     
    +   private interface SnapshotStrategySynchronicityBehavior<K> {
    +
    +           default void finalizeSnapshotBeforeReturnHook(Runnable 
runnable) {
    +
    +           }
    +
    +           default void logOperationCompleted(CheckpointStreamFactory 
streamFactory, long startTime) {
    +
    +           }
    +
    +           boolean isAsynchronous();
    +
    +           <N, V> StateTable<K, N, V> 
newStateTable(RegisteredKeyedBackendStateMetaInfo<N, V> newMetaInfo);
    --- End diff --
    
    I think this method should be part of the `SnapshotStrategy` interface. 
That way we would make the `SnapshotStrategySynchronicityBehavior` sub classes 
independent of the `HeapKeyedStateBackend`.


> 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
>            Priority: Major
>             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
(v7.6.3#76005)

Reply via email to