hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brock Noland <br...@cloudera.com>
Subject Re: Namenode in inconsistent state: how to reinitialize the storage directory
Date Wed, 26 Oct 2011 10:48:12 GMT
Moving this discussion to CDH-USER since it sounds like it's the Cloudera VM.

BCC mapreduce-user

On Wed, Oct 26, 2011 at 2:17 AM, Stephen Boesch <javadba@gmail.com> wrote:
> I found a suggestion to reformat the namenode.  In order to do so, I found
> it necessary to set the dir to 777. AFter
> $ sudo chmod 777 /var/lib/hadoop-0.20/cache/hadoop/dfs/name
> $ ./hadoop namenode -format

What user was this executed as?  In the VM & CDH package install
NameNode/DataNode run as hdfs while JobTracker/TaskTracker run as

As such, if you executed the format command as:

sudo -u hdfs

You shouldn't need 777 permissions.

> (successful)
> $ ./hadoop-daemon.sh --config $HADOOP/conf start namenode
> (success!)

CDH comes with init startup scripts:


However, based on the commands you have executed above, at this point,
I think you'd need to some chow'ing to use the init scripts.

> So.. this leads to a related question:  What gives with these permissions?
>    Maybe  this is cloudera specific.   I am logged in to cloudera user,. but
> these directories have owners/groups with a mix of hadoop, mapred, hbase,
> hdfs, etc.    When i look in /etc/passwd and /etc/group there is no clear
> indication that cloudera should be able to access files owned by members of
> those groups.
> Where is there more info about making the file permissions happy when
> running the various hadoop services from cloudera user ?
> i am on CDH3u1

NameNode/DataNode run as hdfs while JobTracker/TaskTracker run as mapred


View raw message