Hadoop: Format aborted in /mnt/hdfs/1/namenode -



Hadoop: Format aborted in /mnt/hdfs/1/namenode -

i've created few ebs filesystems on ec2 utilize hadoop. i've set jave_home in hadoop environment. when go format first volume aborts next message

[root@hadoop-node01 conf]# sudo -u hdfs hadoop namenode -format 13/02/06 15:33:22 info namenode.namenode: startup_msg: /************************************************************ startup_msg: starting namenode startup_msg: host = hadoop-node01.mydomain.com/10.xx.xx.201 startup_msg: args = [-format] startup_msg: version = 0.20.2-cdh3u5 startup_msg: build = file:///data/1/tmp/topdir/build/hadoop-0.20.2-cdh3u5 -r 30233064aaf5f2492bc687d61d72956876102109; compiled 'root' on fri oct 5 18:45:46 pdt 2012 ************************************************************/ re-format filesystem in /mnt/hdfs/1/namenode ? (y or n) y format aborted in /mnt/hdfs/1/namenode 13/02/06 15:33:27 info namenode.namenode: shutdown_msg: /************************************************************ shutdown_msg: shutting downwards namenode @ hadoop-node01.mydomain.com/10.xx.xx.201 ************************************************************/

this namenode configuration:

<?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> <!-- set site-specific property overrides in file. --> <configuration> <property> <name>dfs.name.dir</name> <value>/mnt/hdfs/1/namenode,/mnt/hdfs/2/namenode,/mnt/hdfs/3/namenode,/mnt/hdfs/4/namenode</value> </property> <property> <name>dfs.data.dir</name> <value>/mnt/hdfs/1/datanode,/mnt/hdfs/2/datanode,/mnt/hdfs/3/datanode,/mnt/hdfs/4/datanode</value> </property> </configuration>

does have thought why error happening or how around problem?

unfortunately in 1.x format command's prompt case-sensitive. reply capital y instead , won't abort.

hadoop

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -