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

vinoyang commented on FLINK-7641:
---------------------------------

yes [~elevy] you are right, our implementation go further than your 
description, we do not need pause running jobs, the running jobs are still 
running when the master JM failover.

> 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)

Reply via email to