[ https://issues.apache.org/jira/browse/SPARK-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-672. ----------------------------- Resolution: Duplicate The right-er answer is to fail for lack of memory faster, per SPARK-1989. > Executor gets stuck in a "zombie" state after running out of memory > ------------------------------------------------------------------- > > Key: SPARK-672 > URL: https://issues.apache.org/jira/browse/SPARK-672 > Project: Spark > Issue Type: Bug > Components: Spark Core > Reporter: Mikhail Bautin > Attachments: executor_jstack.txt, executor_stderr.txt, > standalone_worker_jstack.txt > > > As a result of running a workload, an executor ran out of memory, but the > executor process stayed up. Also (not sure this is related) the standalone > worker process stayed up but disappeared from the master web UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org