[
https://issues.apache.org/jira/browse/FLINK-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7641:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Runtime / Coordination
> Affects Versions: 1.3.2
> Reporter: Elias Levy
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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
(v8.20.1#820001)
