[
https://issues.apache.org/jira/browse/FLINK-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375179#comment-16375179
]
Elias Levy commented on FLINK-7641:
-----------------------------------
I mean that if you have a standalone cluster in HA mode with multiple JMs, if
the current master JM fails, any jobs executing in the cluster will be stopped
and then restored by the new master JM. Ideally master JM failover should be
largely invisible to running jobs. At most, they should be temporary paused
and continued, rather than stopped and restarted.
> Loss of JobManager in HA mode should not cause jobs to fail
> -----------------------------------------------------------
>
> Key: FLINK-7641
> URL: https://issues.apache.org/jira/browse/FLINK-7641
> Project: Flink
> Issue Type: Improvement
> Components: JobManager
> Affects Versions: 1.3.2
> Reporter: Elias Levy
> Assignee: vinoyang
> Priority: Major
>
> Currently if a standalone cluster of JobManagers is configured in
> high-availability mode and the master JM is lost, the job executing in the
> cluster will be restarted. This is less than ideal. It would be best if the
> jobs could continue to execute without restarting while one of the spare JMs
> becomes the new master, or in the worse case, the jobs are paused while the
> JM election takes place.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
