You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by long hong <gn...@gmail.com> on 2010/11/22 05:06:08 UTC
Namenode cannot start in hadoop0.20.2
hi all, I am recently developing a web app based on Hadoop DFS. I just use one node for dev and find the namenode usualy cannot be started using bin/start-all.sh. I have to frequently reformat the namenode and restart hadoop to make the it work.
Did anyone encounter the same problem? thx for helping !
Re: Namenode cannot start in hadoop0.20.2
Posted by long hong <lo...@gmail.com>.
Oh I just let it be the default value... Thx! :-)
On Nov 22, 2010, at 2:03 PM, Harsh J wrote:
> Hi,
>
> On Mon, Nov 22, 2010 at 9:36 AM, long hong <gn...@gmail.com> wrote:
>> hi all, I am recently developing a web app based on Hadoop DFS. I just use one node for dev and find the namenode usualy cannot be started using bin/start-all.sh. I have to frequently reformat the namenode and restart hadoop to make the it work.
>>
>> Did anyone encounter the same problem? thx for helping !
>
> What is your dfs.name.dir set to? If it is left as default, it resides
> in /tmp and gets wiped out every boot, which should be one cause of
> NameNode not starting again.
>
> --
> Harsh J
> www.harshj.com
Re: Namenode cannot start in hadoop0.20.2
Posted by Harsh J <qw...@gmail.com>.
Hi,
On Mon, Nov 22, 2010 at 9:36 AM, long hong <gn...@gmail.com> wrote:
> hi all, I am recently developing a web app based on Hadoop DFS. I just use one node for dev and find the namenode usualy cannot be started using bin/start-all.sh. I have to frequently reformat the namenode and restart hadoop to make the it work.
>
> Did anyone encounter the same problem? thx for helping !
What is your dfs.name.dir set to? If it is left as default, it resides
in /tmp and gets wiped out every boot, which should be one cause of
NameNode not starting again.
--
Harsh J
www.harshj.com