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

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

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

    https://github.com/apache/flink/pull/5239#discussion_r159861671
  
    --- Diff: 
flink-contrib/flink-statebackend-rocksdb/src/test/java/org/apache/flink/contrib/streaming/state/RocksDBAsyncSnapshotTest.java
 ---
    @@ -132,21 +135,15 @@ public String getKey(String value) throws Exception {
                final OneShotLatch delayCheckpointLatch = new OneShotLatch();
                final OneShotLatch ensureCheckpointLatch = new OneShotLatch();
     
    -           StreamMockEnvironment mockEnv = new StreamMockEnvironment(
    -                           testHarness.jobConfig,
    -                           testHarness.taskConfig,
    -                           testHarness.memorySize,
    -                           new MockInputSplitProvider(),
    -                           testHarness.bufferSize) {
    +           CheckpointResponder checkpointResponderMock = new 
CheckpointResponder() {
    --- End diff --
    
    Is this change relevant to others?


> 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
(v6.4.14#64029)

Reply via email to