[
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557192#comment-17557192
]
Yangze Guo commented on FLINK-19358:
------------------------------------
Hi, there. I'd like to revive this topic for FLIP-241. In the current
implementation, the constant {{jobId}} will confuse the HistoryServer because
it assumed the JobID is unique.
After an offline discussion with [~wangyang0918], we propose to generate a
random JobID at the Flink client when users do not configure one in HA mode. In
this way:
- we keep the consistency of the JobID across failover.
- do not need to introduce special cases in the recovery progress.
- do not have potential conflict with the existing design for supporting the
multiple-execute applications.
> 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
> Assignee: Yangze Guo
> 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.7#820007)
