[
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212257#comment-17212257
]
Till Rohrmann commented on FLINK-19358:
---------------------------------------
We initially did not want to use the {{JobGraphStore}} because the {{JobGraph}}
could be generated from the client code or a serialized {{JobGraph}} which was
accessible by the per-job/application cluster entrypoint. Hence, it seemed
easier to simply regenerate the {{JobGraph}} when restarting the master.
Using the {{JobGraphStore}} could also work for multi-execute applications I
believe. The reason is that successfully finished job parts will reach a
globally terminal state will then be removed from the {{JobGraphStore}}. The
problem is more what happens if the client code fails exactly after the first
part has terminated but the second job was not yet submitted.
> when submit job on application mode with HA,the jobid will be 0000000000
> ------------------------------------------------------------------------
>
> Key: FLINK-19358
> URL: https://issues.apache.org/jira/browse/FLINK-19358
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.11.0
> Reporter: Jun Zhang
> Priority: Major
> Labels: usability
> Fix For: 1.12.0
>
>
> when submit a flink job on application mode with HA ,the flink job id will be
> 00000000000000000000000000000000, when I have many jobs ,they have the same
> job id , it will be lead to a checkpoint error
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
