You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:22:14 UTC
[jira] [Updated] (SPARK-12099) Standalone and Mesos Should use
OnOutOfMemoryError handlers
[ https://issues.apache.org/jira/browse/SPARK-12099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-12099:
---------------------------------
Labels: bulk-closed (was: )
> Standalone and Mesos Should use OnOutOfMemoryError handlers
> -----------------------------------------------------------
>
> Key: SPARK-12099
> URL: https://issues.apache.org/jira/browse/SPARK-12099
> Project: Spark
> Issue Type: Improvement
> Components: Deploy, Mesos
> Affects Versions: 1.6.0
> Reporter: Imran Rashid
> Priority: Major
> Labels: bulk-closed
>
> cc [~andrewor14] [~tnachen]
> On SPARK-11801, we've been discussing the use of {{OnOutMemoryError}} to terminate the jvm in yarn mode. There seems to be consensus that this is indeed the right thing to do. I assume that the other cluster managers should also be doing the same thing. Though maybe there is a good reason for not including it under standalone & mesos mode (or perhaps this is already happening via some other mechanism I'm not seeing). In any case, I thought it was worth drawing your attention to it, I didn't see this discussed in any previous issue.
> (Note that there are currently some drawbacks to using {{OnOutOfMemoryError}}, in that you get some confusing msgs, but hopefully SPARK-11801 will address that.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org