[
https://issues.apache.org/jira/browse/FLINK-19358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200074#comment-17200074
]
Kostas Kloudas commented on FLINK-19358:
----------------------------------------
[~zhangjun] Just as a clarification, you have a single application (a single
{{main()}}) with multiple {{execute()}} calls and HA enabled?
And to answer why we did not support this: The reason is that in this case, if
we have a mix of bounded and unbounded jobs, and some of them finish, some of
them are running and some have not even started, in case of recovery you may
have weird behaviour, as described here:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-85+Flink+Application+Mode
{quote}The added complexity stems mainly from the fact that the different jobs
within an application may at any point be in different stages of their
execution, e.g. some may be running, some finished and some may be waiting for
others to finish in order to consume their output. Supporting savepoints and
fault-tolerance/high-availability in these settings would require (partially)
re-implementing a workflow management system like Airflow within Flink.{quote}
> 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
> 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)
