giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Vesse (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GIRAPH-795) NPE when trying to run Giraph YARN when no Zookeeper configuration is supplied
Date Wed, 13 Nov 2013 15:53:24 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Vesse updated GIRAPH-795:
-----------------------------

    Attachment: GIRAPH-795.patch

Patch which avoids the NPE

> NPE when trying to run Giraph YARN when no Zookeeper configuration is supplied
> ------------------------------------------------------------------------------
>
>                 Key: GIRAPH-795
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-795
>             Project: Giraph
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Rob Vesse
>             Fix For: 1.1.0
>
>         Attachments: GIRAPH-795.patch
>
>
> If you try and run Giraph compiled for YARN but have not specified any external Zookeeper
settings in your Hadoop configuration files you'll receive the following error:
> Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.giraph.yarn.GiraphYarnClient.checkJobLocalZooKeeperSupported(GiraphYarnClient.java:460)
> 	at org.apache.giraph.yarn.GiraphYarnClient.run(GiraphYarnClient.java:116)
> 	at org.apache.giraph.GiraphRunner.run(GiraphRunner.java:96)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> 	at org.apache.giraph.GiraphRunner.main(GiraphRunner.java:126)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
> This looks to be a trivial fix for which I will attach a proposed patch



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message