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

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_r165318377
  
    --- Diff: 
flink-streaming-java/src/test/java/org/apache/flink/streaming/runtime/tasks/StreamTaskTerminationTest.java
 ---
    @@ -227,21 +229,13 @@ protected void cleanup() throws Exception {
                        // has been stopped
                        CLEANUP_LATCH.trigger();
     
    -                   // wait until handle async exception has been called to 
proceed with the termination of the
    -                   // StreamTask
    -                   HANDLE_ASYNC_EXCEPTION_LATCH.await();
    +                   // wait until all async checkpoint threads are 
terminated, so that no more exceptions can be reported
    +                   
Assert.assertTrue(getAsyncOperationsThreadPool().awaitTermination(30L, 
TimeUnit.SECONDS));
    --- End diff --
    
    Where do we trigger the shut down of the `getAsyncOperationsThreadpool`?


> 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