[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
