[
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211535#comment-17211535
]
Yang Wang commented on FLINK-19358:
-----------------------------------
Specifying a different job id for every job via {{execute()}} is not very easy
to use. Actually, in our production environment, we are adding the cluster-id
to the {{state.checkpoints.dir}}. For example, it could be
{{hdfs:///flink/checkpoints/application_xxxx}} on YARN or
{{oss://flink/checkpoints/native-k8s-app1}} for K8s.
[~kkl0u] Actually I have a question about the fixed job id. We could recover
job ids and job graphs from JobGraphStore when HA enabled. So I am not sure why
we still need to set the fixed ZERO job id. Could we directly use the recovered
job id to get the job client?
> 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)
