[ https://issues.apache.org/jira/browse/FLINK-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313157#comment-16313157 ]
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_r159880011 --- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/state/CheckpointStreamFactory.java --- @@ -43,9 +44,9 @@ CheckpointStateOutputStream createCheckpointStateOutputStream( * Closes the stream factory, releasing all internal resources, but does not delete any * persistent checkpoint data. * - * @throws Exception Exceptions can be forwarded and will be logged by the system + * @throws IOException Exceptions can be forwarded and will be logged by the system */ - void close() throws Exception; + void close() throws IOException; --- End diff -- What's this change for? Is it used anywhere? It seems to me like `close()` is just a dead code and this method could be dropped, or did I missed something? > 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)