Solved it. IIUC that is because, by default, the conf/ subdirectory is not part of classpath in 0.23. You need to specify it using the --config switch:
$ hdfs --config ~/hadoop/conf/ namenode whereas before you'd have typed $ hadoop namenode On Wed, Nov 16, 2011 at 1:33 PM, Petru Dimulescu <petru.dimule...@gmail.com> wrote: > Hello, > > I had a simple one-node configuration for 0.20, base of two files, > located in conf/: > > core-site.xml : > > <configuration> > <property> > <name>fs.default.name</name> > <value>hdfs://192.168.1.107:8999</value> > </property> > </configuration> > > hdfs-site.xml : > > <configuration> > <property> > <name>dfs.data.dir</name> > <value>/stuff/hadoop/data</value> > </property> > <property> > <name>dfs.name.dir</name> > <value>/stuff/hadoop/name</value> > </property> > </configuration> > > > If I use the same configuration with 0.23 it doesn't work -- when I > launch "./hdfs namenode" I get the catch-all exception: > > java.lang.IllegalArgumentException: Invalid URI for NameNode address > (check fs.defaultFS): file:/// has no authority. > > 0.23 doc says "Federation configuration is backward compatible and > allows existing single Namenode configuration to work without any > change." > (http://hadoop.apache.org/common/docs/r0.23.0/hadoop-yarn/hadoop-yarn-site/Federation.html#Federation_Configuration) > > Any idea? >
