i am facing a similar issue. when the job runs with partitions > num of cores then sometimes the executors are getting lost and the job doesnt complete. is there any additional logging that can be turned on to see the exact cause of this issue?
-- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Spark-partition-issue-with-Stanford-NLP-tp23048p23055.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
