[
https://issues.apache.org/jira/browse/FLINK-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5230:
----------------------------------
Labels: auto-deprioritized-major (was: stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Safety nets against leaving dysfunctional JobManagers
> -----------------------------------------------------
>
> Key: FLINK-5230
> URL: https://issues.apache.org/jira/browse/FLINK-5230
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Stephan Ewen
> Priority: Minor
> Labels: auto-deprioritized-major
>
> There are certain ways that a {{JobManager}} can become dysfunctional.
> If the JobManager process continues to exist (not restarted by YARN / Mesos)
> etc, but is not doing its work properly and more, it makes the Streaming Job
> unavailable.
> There some safety nets to bring into place for that, see sub issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
