You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by "Christian Goetze (CG)" <cg...@lindenlab.com> on 2008/03/07 03:26:25 UTC

Trouble getting namenode to run

It must be something trivial, but please be patient with a 
hadoop-noob... it fails on

String newAddrPort = conf.get(newBindAddressName)

at
2008-03-06 17:59:21,087 ERROR org.apache.hadoop.dfs.NameNode: 
java.lang.NullPointerException
        at 
org.apache.hadoop.net.NetUtils.getServerAddress(NetUtils.java:148)
        at 
org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:279)
        at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
        at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
        at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
        at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)


so, what configuration am i missing?

Thanks in Advance!
--
cg

Re: Trouble getting namenode to run

Posted by Michael Bieniosek <mi...@powerset.com>.
This looks like a bug in hadoop.  You should file a JIRA at
https://issues.apache.org/jira/secure/CreateIssue!default.jspa

Meanwhile, try setting your fs.default.name to sim1.dev.lindenlab.com:54310

-Michael

On 3/6/08 6:33 PM, "Christian Goetze (CG)" <cg...@lindenlab.com> wrote:

> Christian Goetze (CG) wrote:
>> It must be something trivial, but please be patient with a
>> hadoop-noob... it fails on
>>
>> String newAddrPort = conf.get(newBindAddressName)
>>
>> at
>> 2008-03-06 17:59:21,087 ERROR org.apache.hadoop.dfs.NameNode:
>> java.lang.NullPointerException
>>        at
>> org.apache.hadoop.net.NetUtils.getServerAddress(NetUtils.java:148)
>>        at
>> org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:279)
>>        at
>> org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
>>        at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
>>        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
>>        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
>>        at
>> org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
>>        at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)
>>
>>
>> so, what configuration am i missing?
>>
>> Thanks in Advance!
>> --
>> cg
>>
> Oh, and I'm running 0.16, and this is the current hadoop-site.xml:
>
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
>
> <!-- Put site-specific property overrides in this file. -->
>
> <configuration>
>
> <property>
>   <name>hadoop.tmp.dir</name>
>   <value>/local/hadoop/data</value>
>   <description>A base for other temporary directories.</description>
> </property>
>
> <property>
>   <name>fs.default.name</name>
>   <value>hdfs://sim1.dev.lindenlab.com:54310/</value>
>   <description>The name of the default file system.  A URI whose
>   scheme and authority determine the FileSystem implementation.  The
>   uri's scheme determines the config property (fs.SCHEME.impl) naming
>   the FileSystem implementation class.  The uri's authority is used to
>   determine the host, port, etc. for a filesystem.</description>
> </property>
>
> <property>
>   <name>mapred.job.tracker</name>
>   <value>sim1.dev.lindenlab.com:54311</value>
>   <description>The host and port that the MapReduce job tracker runs
>   at.  If "local", then jobs are run in-process as a single map
>   and reduce task.
>   </description>
> </property>
>
> <property>
>   <name>dfs.replication</name>
>   <value>2</value>
>   <description>Default block replication.
>   The actual number of replications can be specified when the file is
> created.
>   The default is used if replication is not specified in create time.
>   </description>
> </property>
>
> <property>
>   <name>mapred.map.tasks</name>
>   <!-- "As a rule of thumb, use 10x the number of slaves (i.e., number
> of tasktrackers)."
>        - Michael Noll,
>
> http://www.michael-noll.com/wiki/Running_Hadoop_On_Ubuntu_Linux_%28Multi-Node_
> Cluster%29
>   -->
>   <value>50</value>
> </property>
>
> <property>
>   <name>mapred.reduce.tasks</name>
>   <!-- "As a rule of thumb, use 2x the number of slave processors (i.e.,
> number of tasktrackers)."
>        - ibid.
>   -->
>   <value>10</value>
> </property>
>
>
>

Re: Trouble getting namenode to run

Posted by "Christian Goetze (CG)" <cg...@lindenlab.com>.
Christian Goetze (CG) wrote:
> It must be something trivial, but please be patient with a 
> hadoop-noob... it fails on
>
> String newAddrPort = conf.get(newBindAddressName)
>
> at
> 2008-03-06 17:59:21,087 ERROR org.apache.hadoop.dfs.NameNode: 
> java.lang.NullPointerException
>        at 
> org.apache.hadoop.net.NetUtils.getServerAddress(NetUtils.java:148)
>        at 
> org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:279)
>        at 
> org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
>        at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
>        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
>        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
>        at 
> org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
>        at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)
>
>
> so, what configuration am i missing?
>
> Thanks in Advance!
> -- 
> cg
>
Oh, and I'm running 0.16, and this is the current hadoop-site.xml:

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>

<!-- Put site-specific property overrides in this file. -->

<configuration>

<property>
  <name>hadoop.tmp.dir</name>
  <value>/local/hadoop/data</value>
  <description>A base for other temporary directories.</description>
</property>
 
<property>
  <name>fs.default.name</name>
  <value>hdfs://sim1.dev.lindenlab.com:54310/</value>
  <description>The name of the default file system.  A URI whose
  scheme and authority determine the FileSystem implementation.  The
  uri's scheme determines the config property (fs.SCHEME.impl) naming
  the FileSystem implementation class.  The uri's authority is used to
  determine the host, port, etc. for a filesystem.</description>
</property>
 
<property>
  <name>mapred.job.tracker</name>
  <value>sim1.dev.lindenlab.com:54311</value>
  <description>The host and port that the MapReduce job tracker runs
  at.  If "local", then jobs are run in-process as a single map
  and reduce task.
  </description>
</property>
 
<property>
  <name>dfs.replication</name>
  <value>2</value>
  <description>Default block replication.
  The actual number of replications can be specified when the file is 
created.
  The default is used if replication is not specified in create time.
  </description>
</property>

<property>
  <name>mapred.map.tasks</name>
  <!-- "As a rule of thumb, use 10x the number of slaves (i.e., number 
of tasktrackers)."
       - Michael Noll,
         
http://www.michael-noll.com/wiki/Running_Hadoop_On_Ubuntu_Linux_%28Multi-Node_Cluster%29
  -->
  <value>50</value>
</property>

<property>
  <name>mapred.reduce.tasks</name>
  <!-- "As a rule of thumb, use 2x the number of slave processors (i.e., 
number of tasktrackers)."
       - ibid.
  -->
  <value>10</value>
</property>