[
https://issues.apache.org/jira/browse/SPARK-11022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated SPARK-11022:
---------------------------------
Labels: bulk-closed (was: )
> Spark Worker need improve the executor garbage while the app has massive
> failures
> ----------------------------------------------------------------------------------
>
> Key: SPARK-11022
> URL: https://issues.apache.org/jira/browse/SPARK-11022
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 1.4.0
> Reporter: colin shaw
> Priority: Minor
> Labels: bulk-closed
>
> Worker process often down,while there were not any abnormal tasks，just crash
> without anymessage， after added "-XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=${SPARK_HOME}/logs", a dump file show there is "17,010
> instances of "org.apache.spark.deploy.worker.ExecutorRunner", loaded by
> "sun.misc.Launcher$AppClassLoader @ 0xe2abfcc8" occupy 496,706,920 (96.14%)
> bytes. "
> and almost all the instance were stored in a
> "org.apache.spark.deploy.worker.Worker" instance, the finishedExecutors field
> hold many ExecutorRunner.
> The codes(Worker.scala) shows finishedExecutors just
> "finishedExecutors(fullId) = executor" and
> "finishedExecutors.values.toList",there is no action which remove the
> Executor,all were stored in memory,so after receive many executors status
> report,may cause crash,I think this need improved.
> tks~ & best regards
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
