[ 
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450172#comment-17450172
 ] 

Yang Wang commented on FLINK-19358:
-----------------------------------

IIUC, whether to recover or submit a new job is determined in 
{{{}EmbeddedExecutor#execute{}}}. If the HA is enabled, we could rely on the 
submitted jobs from {{JobGraphStore}} and have a simpler behavior like 
following.
{code:java}
if (submittedJobIds.size() > 0) {
    // We expect only 1 recovered job here
    return getJobClientFuture(submittedJobIds.iterator().next(), 
userCodeClassloader);
} else {
    return submitAndGetJobClientFuture(pipeline, configuration, 
userCodeClassloader);
}{code}
 

Of cause, we also need to change a bit {{ApplicationDispatcherBootstrap}} about 
not to set the {{PIPELINE_FIXED_JOB_ID}} to ZERO internally.

> 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: Runtime / Coordination
>    Affects Versions: 1.11.0
>            Reporter: Jun Zhang
>            Priority: Minor
>              Labels: auto-deprioritized-major, usability
>
> 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.20.1#820001)

Reply via email to