I've seen these caused by the OOM killer. I recommend checking /var/log/syslog to see if it was activated due to lack of system memory.
On Thu, Jun 12, 2014 at 11:45 PM, libl <271592...@qq.com> wrote: > I use standalone mode submit task.But often,I got an error.The stacktrace as > > 2014-06-12 11:37:36,578 [INFO] [org.apache.spark.Logging$class] > [Method:logInfo] [Line:49] [Thread:spark-akka.actor.default-dispatcher-18] > - Executor updated: app-20140612092238-0007/0 is now FAILED (Command exited > with code 137) > 2014-06-12 11:37:36,670 [INFO] [org.apache.spark.Logging$class] > [Method:logInfo] [Line:49] [Thread:spark-akka.actor.default-dispatcher-18] > - Executor app-20140612092238-0007/0 removed: Command exited with code 137 > 2014-06-12 11:37:36,673 [INFO] [org.apache.spark.Logging$cla0ss] > [Method:logInfo] [Line:49] [Thread:spark-akka.actor.default-dispatcher-15] > - Executor 0 disconnected, so removing it > 2014-06-12 11:37:36,682 [ERROR] [org.apache.spark.Logging$class] > [Method:logError] [Line:65] [Thread:spark-akka.actor.default-dispatcher-15] > - Lost executor 0 on tj-hadoop-1.certus.com: Unknown executor exit code > (137) (died from signal 9?) > > > spark config is > spark_worker_timeout=300 > spark_akka_timeout=500 > spark_akka_frameSize=1000 > spark_akka_num_retries=30 > spark_akka_askTimeout=300 > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/Command-exited-with-code-137-tp7557.html > Sent from the Apache Spark User List mailing list archive at Nabble.com.
