*SOLVED:* Unfortunately, stderr log in Hadoop's Resource Manager UI was not useful since it just reported "... Lost executor XX on workerYYY...". Therefore, I dumped locally the whole app-related logs: /yarn logs -applicationId application_1458320004153_0343 > ~/application_1458320004153_0343.txt/. That log is split by container and I've noticed that each "workerYYY" had a WARN and an sudden crash after a bit.
Some "Untokenizable" chars in the /email.body/ made CoreNLP throw a WARN at first and then crash/loose the executor after a few seconds. This happened systematically and I think it is a bug in CoreNLP 3.4.1. The solution was just sanitise the input fed to the Annotation constructor. -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Stanford-CoreNLP-sentiment-extraction-lost-executor-tp26536p26541.html Sent from the Apache Spark User List mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
