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-5231) JobManager should exit on "OutOfMemoryError"

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

Andrey Zagrebin reassigned FLINK-5231:
--------------------------------------

    Assignee:     (was: vinoyang)

> JobManager should exit on "OutOfMemoryError"
> --------------------------------------------
>
>                 Key: FLINK-5231
>                 URL: https://issues.apache.org/jira/browse/FLINK-5231
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.1.3
>            Reporter: Stephan Ewen
>            Priority: Major
>
> A JobManager that ever encountered an {{OutOfMemoryError}} is with a high probability not functional any more. However, the {{OutOfMemoryError}} kills only the thread where it is thrown by default, not the entire JVM.
> We should add {{-XX:OnOutOfMemoryError="kill -9 %p"}} both to the standalone bash options and to the YARN and Mesos launch options.
> On the TaskManager side, the decision is more tricky and less critical, so I suggest to add this only to the JobManager by default.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)