[
https://issues.apache.org/jira/browse/FLINK-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728937#comment-14728937
]
ASF GitHub Bot commented on FLINK-2615:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1088#issuecomment-137420928
Aha. I just had a brief look at the PR.
I had initially thought of implementing a start and stop method in the
`ExecutionEnvironment` but decided against it, since it changes the api for
very minor changes.
Session management is a way better solution. Any timeline on when those
changes could get merged?
> Multiple restarts of Local Cluster for a single program
> -------------------------------------------------------
>
> Key: FLINK-2615
> URL: https://issues.apache.org/jira/browse/FLINK-2615
> Project: Flink
> Issue Type: Bug
> Reporter: Sachin Goel
> Assignee: Sachin Goel
>
> Currently, the LocalExecutor which executes program in a local environment
> starts a new cluster and tears it down on every call to execute. This can
> take up a lot of time since a program might trigger execution several times.
> Further, it is semantically different from the RemoteExecutor as in the
> latter, the actors always stay the same.
> A restart of actors in itself prevents any sharing of results across
> different executions. [A Persist operation.]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
