[ 
https://issues.apache.org/jira/browse/SPARK-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380919#comment-14380919
 ] 

Sean Owen commented on SPARK-6539:
----------------------------------

Hm, I can't reproduce that. I'm running Java 8u40 too and ran this exactly as a 
simple program from the IDE (I set appName to "foo"). It did not throw any 
exception. Is anything else going on like earlier errors? can you tell exactly 
what's {{null}}? that might at least give a better clue. I think the only thing 
that can NPE on that line is a null {{SparkEnv.env}} but that's clearly set 
earlier in the constructor.

> SparkContext throws NullPointerException
> ----------------------------------------
>
>                 Key: SPARK-6539
>                 URL: https://issues.apache.org/jira/browse/SPARK-6539
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.3.0
>         Environment: Spark built using the folllowing:
> {code}
> ./make-distribution.sh --tgz -Pyarn -Phadoop-2.2 -Dhadoop.version=2.2.0 
> -DskipTests
> {code}
> Targeting Pivotal HD 2.1 (Hadoop 2.2) cluster with the nodes running JDK 8u40
>            Reporter: davep
>
> The following snippet of the client driver will throw a NullPointerException 
> when trying to create a SparkContext
> {code:java}
> SparkConf conf = new SparkConf().setAppName(appName).setMaster("yarn-client");
> JavaSparkContext sc = new JavaSparkContext(conf);
> {code}
> The exception is thrown when trying to create the block manager source here:
> https://github.com/apache/spark/blob/branch-1.3/core/src/main/scala/org/apache/spark/SparkContext.scala#L544
> If I compile the client driver with JDK7 or JDK8 it throws the same 
> exception. Changing the JDK on the Hadoop cluster to v7 resolves this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to