[
https://issues.apache.org/jira/browse/FLINK-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322297#comment-16322297
]
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_r160940119
--- Diff:
flink-runtime/src/test/java/org/apache/flink/runtime/operators/testutils/DummyEnvironment.java
---
@@ -53,10 +54,15 @@
private final ExecutionConfig executionConfig = new ExecutionConfig();
private final TaskInfo taskInfo;
private KvStateRegistry kvStateRegistry = new KvStateRegistry();
+ private TaskStateManager taskStateManager;
--- End diff --
Can not this variable be made final and set in the constructor? From what I
have checked in the usages it seems like it could be so, since all use cases
are:
```
{
TaskStateManager taskStateManager = ....;
// (...)
DummyEnvironment environment = new DummyEnvironment(...);
// (...)
environment. setTaskStateManager(taskStateManager);
}
```
> 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)
