flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From shixiaogang <...@git.apache.org>
Subject [GitHub] flink pull request #3801: [FLINK-6364] [checkpoints] Implement incremental c...
Date Wed, 03 May 2017 14:54:20 GMT
Github user shixiaogang commented on a diff in the pull request:

    --- Diff: flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/tasks/StreamTask.java
    @@ -769,9 +769,10 @@ public OperatorStateBackend createOperatorStateBackend(
     		// restore if we have some old state
    -		if (null != restoreStateHandles && null != restoreStateHandles.getManagedKeyedState())
    -			keyedStateBackend.restore(restoreStateHandles.getManagedKeyedState());
    -		}
    +		Collection<KeyedStateHandle> restoreKeyedStateHandles =
    +			restoreStateHandles == null ? null : restoreStateHandles.getManagedKeyedState();
    +		keyedStateBackend.restore(restoreKeyedStateHandles);
    --- End diff --
    I attempted to put the restore state in the constructor as we discussed. But it turns
out impossible. 
    All state backends should be registered in the task so that the backends can be closed
when the task is canceled.  If we put the restoring in the constructor of the backends, the
construction of the backends may be blocked (e.g., due to the access to HDFS). Since the construction
is not completed yet, the backend will not be registered and hence will not be closed.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message