Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.1.3
-
None
-
None
Description
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.
Hi sewen the JDK8, (more precisely since JDK 8u92, pelase see : http://www.oracle.com/technetwork/java/javase/8u92-relnotes-2949471.html), there are two new JVM options:
I think for old JDK we can use 'OnOutOfMemoryError' option, however, higher JDK these options would be better to fix the OOMError.
What's your opinion?