[
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212261#comment-17212261
]
Kostas Kloudas commented on FLINK-19358:
----------------------------------------
[~trohrmann] I agree and this is what I had in my mind when I wrote the comment
above (although now that I re-read it it is not clear). And actually this can
be a common case because most jobs use the {{execute()}} call which is
blocking. So the "next" will wait for the "previous" to be finished before
being submitted.
So from the proposed solutions:
1) always appending the {{cluster-id}} to the {{state.checkpoints.dir}}, and
2) allowing the user to specify a {{JobId}} in the {{execute()}}
You lean towards the first, right [~trohrmann]?
> 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)
