[jira] [Updated] (FLINK-5230) Safety nets against leaving dysfunctional JobManagers

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-5230:
----------------------------------
    Labels: stale-major  (was: )

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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Major
>              Labels: stale-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)