Sorry for the extremely late reply. It turns out that the same error occurred
when running on yarn. However, I recently updated my project to depend on
cdh5 and the issue I was having disappeared and I am no longer setting the
userClassPathFirst to true.
--
View this message in context:
-tp11917p12008.html
To unsubscribe from spark.files.userClassPathFirst=true Not Working
Correctly, click here
http://apache-spark-user-list.1001560.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=11917code=ZGFuaWVsQHdpYmlkYXRhLmNvbXwxMTkxN3wyMDg5NTg4OTMz
.
NAML
http://apache-spark
Hi, sorry for the delay. Would you have yarn available to test? Given
the discussion in SPARK-2878, this might be a different incarnation of
the same underlying issue.
The option in Yarn is spark.yarn.user.classpath.first
On Mon, Aug 11, 2014 at 1:33 PM, DNoteboom dan...@wibidata.com wrote:
I'm
Could you share what's the cluster manager you're using and exactly
where the error shows up (driver or executor)?
A quick look reveals that Standalone and Yarn use different options to
control this, for example. (Maybe that already should be a bug.)
On Mon, Aug 11, 2014 at 12:24 PM, DNoteboom
I'm currently running on my local machine on standalone. The error shows up
in my code when I am closing resources using the
TaskContext.addOnCompleteCallBack. However, the cause of this error is
because of a faulty classLoader which must occur in the Executor in the
function createClassLoader.
