[
https://issues.apache.org/jira/browse/FLINK-10292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633959#comment-16633959
]
Till Rohrmann commented on FLINK-10292:
---------------------------------------
I see your point [~uce].
Conceptually, it would be easier to simply generate the {{JobGraph}} anew when
starting the container entrypoint. However, this approach has the requirement
that the {{JobGraph}} generation is side-effect free. Consequently, the more
general solution would be to use a proper HA store to store the {{JobGraph}}
and requiring the user to clean up HA data if he wants to upgrade the job.
A solution could be to actually offer both behaviours in the
{{StandaloneJobClusterEntrypoint}}. One would be the default and the other
option needs to be explicitly activated (e.g. if you know that your jobs are
side-effect free).
> 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.7.0, 1.6.2
>
>
> 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)
