[
https://issues.apache.org/jira/browse/FLINK-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-4312.
---------------------------------
Resolution: Fixed
Fixed via c9b0dad89b79f11ce13fe78f8a0823b8266f930f
(Commit has JIRA issue tag of parent issue, not of subtask)
> Remove Serializabiliy of ExecutionGraph
> ---------------------------------------
>
> Key: FLINK-4312
> URL: https://issues.apache.org/jira/browse/FLINK-4312
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager
> Affects Versions: 1.1.0
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Minor
> Fix For: 1.2.0
>
>
> As a preparatory task for reworking the {{ExecutionGraph}} for finer grained
> recovery, I would clean up the serializability:
> - As long as a job is running, the ExecutionGraph cannot be serializable
> - Once it is completed, the ExecutionGraph is sent to a local archive
> actor. This does not require that the graph is serializable.
> - In the future, archived execution data should be served from a static
> dump of the execution data anyways, not from an archived graph. That allows
> us to move the web monitor server to a separate trusted process (gateway /
> dispatcher) that will never be in touch with user code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
