GitHub user manku-timma opened a pull request:
https://github.com/apache/spark/pull/322
[SPARK-1403] Move the class loader creation back to where it was in 0.9.0
[SPARK-1403] I investigated why spark 0.9.0 loads fine on mesos while spark
1.0.0 fails. What I found was that in SparkEnv.scala, while creating the
SparkEnv object, the current thread's classloader is null. But in 0.9.0, at the
same place, it is set to org.apache.spark.repl.ExecutorClassLoader . I saw that
https://github.com/apache/spark/commit/7edbea41b43e0dc11a2de156be220db8b7952d01
moved it to it current place. I moved it back and saw that 1.0.0 started
working fine on mesos.
I just created a minimal patch that allows me to run spark on mesos
correctly. It seems like SecurityManager's creation needs to be taken into
account for a correct fix. Also moving the creation of the serializer out of
SparkEnv might be a part of the right solution. PTAL.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/manku-timma/spark-1 spark-1403
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/322.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #322
----
commit 89109d7bf2ce35e58a252bd7144438fc720ee362
Author: Bharath Bhushan <manku.ti...@outlook.com>
Date: 2014-04-04T02:26:26Z
move the class loader creation back to where it was in 0.9.0
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
