[
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203972#comment-17203972
]
Kostas Kloudas commented on FLINK-19358:
----------------------------------------
[~trohrmann] I do not remember how it was in the old
{{StandaloneJobClusterEntryPoint}} but it is true that we do not need to set a
fixed job id when HA is disabled. I think the problem is
[here|https://github.com/kl0u/flink/blob/master/flink-clients/src/main/java/org/apache/flink/client/deployment/application/ApplicationDispatcherBootstrap.java#L179].
I will open a new issue and open a PR to fix that.
Any comment on how we can bypass the issue here [~trohrmann]? As you said the
problem should not be unique here. One option, which we had discussed in the
past, was to allow the user to specify a "fixed" and unique job id either
through the {{execute}} call or through a config option. But this will not
solve the issue for already running jobs.
> 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)
