[
https://issues.apache.org/jira/browse/FLINK-10292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607983#comment-16607983
]
vinoyang commented on FLINK-10292:
----------------------------------
hi [~till.rohrmann] I personally feel that after fixing FLINK-10291 we have a
known job id. We can consider merging the SingleJobSubmittedJobGraphStore and
the ZooKeeperSubmittedJobGraphStore (or removing the
SingleJobSubmittedJobGraphStore). If we want to store the jobgraph for
recovery, we can reuse the ZooKeeperSubmittedJobGraphStore.
> Generate JobGraph in StandaloneJobClusterEntrypoint only once
> -------------------------------------------------------------
>
> Key: FLINK-10292
> URL: https://issues.apache.org/jira/browse/FLINK-10292
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.6.0, 1.7.0
> Reporter: Till Rohrmann
> Assignee: vinoyang
> Priority: Major
> Fix For: 1.6.1, 1.7.0
>
>
> Currently the {{StandaloneJobClusterEntrypoint}} generates the {{JobGraph}}
> from the given user code every time it starts/is restarted. This can be
> problematic if the the {{JobGraph}} generation has side effects. Therefore,
> it would be better to generate the {{JobGraph}} only once and store it in HA
> storage instead from where to retrieve.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
