You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2020/10/23 09:52:00 UTC

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

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

Andrey Zagrebin reassigned FLINK-5230:
--------------------------------------

    Assignee:     (was: vinoyang)

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