You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-user@hadoop.apache.org by haihong lu <un...@gmail.com> on 2014/03/25 09:51:36 UTC
namenode could not start
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh .
Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
storage directory does not exist or is not accessible.
at
org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
one correct command is: hdfs namenode -format
On Wed, Mar 26, 2014 at 1:58 PM, haihong lu <un...@gmail.com> wrote:
> Yes.But the issue has been fixed, thanks for help.
>
> in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
> format"
>
>
> On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> are you getting same exception..? If do format and then start-dfs.sh..
>>
>>
>>
>> are you using the same config..? I mean, while formatting the namenodeand while starting..
>>
>>
>>
>> can you please check or paste the configurations,exceptions in namenodelog and format log..
>>
>>
>>
>> and hope you are formatting and starting with same user..
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* haihong lu [ung3210@gmail.com]
>> *Sent:* Wednesday, March 26, 2014 7:04 AM
>> *To:* user
>>
>> *Subject:* Re: namenode could not start
>>
>> /home/hadoop/mydata/hdfs/namenode should be created when executed
>> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
>> effect.
>>
>>
>> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
>> brahmareddy.battula@huawei.com> wrote:
>>
>>> Please format the namenode and then do start-dfs..
>>>
>>>
>>>
>>>
>>>
>>> *Command for namenode format:*
>>>
>>>
>>>
>>> hdfs namenode -format
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards
>>>
>>>
>>>
>>> Brahma Reddy Battula
>>>
>>>
>>> ------------------------------
>>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>>> *To:* user@hadoop.apache.org
>>> *Subject:* Re: namenode could not start
>>>
>>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>>> right permission?
>>>
>>>
>>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>>
>>>> Dear all:
>>>>
>>>> I had a problem that the namenode could not start when i ran
>>>> start-dfs.sh . Show the message as below:
>>>>
>>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>>> namenode join
>>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>>> storage directory does not exist or is not accessible.
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>>
>>>> Thank for any help
>>>>
>>>>
>>>
>>
>
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
one correct command is: hdfs namenode -format
On Wed, Mar 26, 2014 at 1:58 PM, haihong lu <un...@gmail.com> wrote:
> Yes.But the issue has been fixed, thanks for help.
>
> in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
> format"
>
>
> On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> are you getting same exception..? If do format and then start-dfs.sh..
>>
>>
>>
>> are you using the same config..? I mean, while formatting the namenodeand while starting..
>>
>>
>>
>> can you please check or paste the configurations,exceptions in namenodelog and format log..
>>
>>
>>
>> and hope you are formatting and starting with same user..
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* haihong lu [ung3210@gmail.com]
>> *Sent:* Wednesday, March 26, 2014 7:04 AM
>> *To:* user
>>
>> *Subject:* Re: namenode could not start
>>
>> /home/hadoop/mydata/hdfs/namenode should be created when executed
>> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
>> effect.
>>
>>
>> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
>> brahmareddy.battula@huawei.com> wrote:
>>
>>> Please format the namenode and then do start-dfs..
>>>
>>>
>>>
>>>
>>>
>>> *Command for namenode format:*
>>>
>>>
>>>
>>> hdfs namenode -format
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards
>>>
>>>
>>>
>>> Brahma Reddy Battula
>>>
>>>
>>> ------------------------------
>>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>>> *To:* user@hadoop.apache.org
>>> *Subject:* Re: namenode could not start
>>>
>>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>>> right permission?
>>>
>>>
>>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>>
>>>> Dear all:
>>>>
>>>> I had a problem that the namenode could not start when i ran
>>>> start-dfs.sh . Show the message as below:
>>>>
>>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>>> namenode join
>>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>>> storage directory does not exist or is not accessible.
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>>
>>>> Thank for any help
>>>>
>>>>
>>>
>>
>
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
one correct command is: hdfs namenode -format
On Wed, Mar 26, 2014 at 1:58 PM, haihong lu <un...@gmail.com> wrote:
> Yes.But the issue has been fixed, thanks for help.
>
> in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
> format"
>
>
> On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> are you getting same exception..? If do format and then start-dfs.sh..
>>
>>
>>
>> are you using the same config..? I mean, while formatting the namenodeand while starting..
>>
>>
>>
>> can you please check or paste the configurations,exceptions in namenodelog and format log..
>>
>>
>>
>> and hope you are formatting and starting with same user..
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* haihong lu [ung3210@gmail.com]
>> *Sent:* Wednesday, March 26, 2014 7:04 AM
>> *To:* user
>>
>> *Subject:* Re: namenode could not start
>>
>> /home/hadoop/mydata/hdfs/namenode should be created when executed
>> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
>> effect.
>>
>>
>> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
>> brahmareddy.battula@huawei.com> wrote:
>>
>>> Please format the namenode and then do start-dfs..
>>>
>>>
>>>
>>>
>>>
>>> *Command for namenode format:*
>>>
>>>
>>>
>>> hdfs namenode -format
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards
>>>
>>>
>>>
>>> Brahma Reddy Battula
>>>
>>>
>>> ------------------------------
>>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>>> *To:* user@hadoop.apache.org
>>> *Subject:* Re: namenode could not start
>>>
>>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>>> right permission?
>>>
>>>
>>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>>
>>>> Dear all:
>>>>
>>>> I had a problem that the namenode could not start when i ran
>>>> start-dfs.sh . Show the message as below:
>>>>
>>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>>> namenode join
>>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>>> storage directory does not exist or is not accessible.
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>>
>>>> Thank for any help
>>>>
>>>>
>>>
>>
>
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
one correct command is: hdfs namenode -format
On Wed, Mar 26, 2014 at 1:58 PM, haihong lu <un...@gmail.com> wrote:
> Yes.But the issue has been fixed, thanks for help.
>
> in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
> format"
>
>
> On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> are you getting same exception..? If do format and then start-dfs.sh..
>>
>>
>>
>> are you using the same config..? I mean, while formatting the namenodeand while starting..
>>
>>
>>
>> can you please check or paste the configurations,exceptions in namenodelog and format log..
>>
>>
>>
>> and hope you are formatting and starting with same user..
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* haihong lu [ung3210@gmail.com]
>> *Sent:* Wednesday, March 26, 2014 7:04 AM
>> *To:* user
>>
>> *Subject:* Re: namenode could not start
>>
>> /home/hadoop/mydata/hdfs/namenode should be created when executed
>> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
>> effect.
>>
>>
>> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
>> brahmareddy.battula@huawei.com> wrote:
>>
>>> Please format the namenode and then do start-dfs..
>>>
>>>
>>>
>>>
>>>
>>> *Command for namenode format:*
>>>
>>>
>>>
>>> hdfs namenode -format
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards
>>>
>>>
>>>
>>> Brahma Reddy Battula
>>>
>>>
>>> ------------------------------
>>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>>> *To:* user@hadoop.apache.org
>>> *Subject:* Re: namenode could not start
>>>
>>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>>> right permission?
>>>
>>>
>>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>>
>>>> Dear all:
>>>>
>>>> I had a problem that the namenode could not start when i ran
>>>> start-dfs.sh . Show the message as below:
>>>>
>>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>>> namenode join
>>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>>> storage directory does not exist or is not accessible.
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>>> at
>>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>>
>>>> Thank for any help
>>>>
>>>>
>>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
Yes.But the issue has been fixed, thanks for help.
in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
format"
On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> are you getting same exception..? If do format and then start-dfs.sh..
>
>
>
> are you using the same config..? I mean, while formatting the namenodeand while starting..
>
>
>
> can you please check or paste the configurations,exceptions in namenodelog and format log..
>
>
>
> and hope you are formatting and starting with same user..
>
>
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* haihong lu [ung3210@gmail.com]
> *Sent:* Wednesday, March 26, 2014 7:04 AM
> *To:* user
>
> *Subject:* Re: namenode could not start
>
> /home/hadoop/mydata/hdfs/namenode should be created when executed
> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
> effect.
>
>
> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> Please format the namenode and then do start-dfs..
>>
>>
>>
>>
>>
>> *Command for namenode format:*
>>
>>
>>
>> hdfs namenode -format
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>> *To:* user@hadoop.apache.org
>> *Subject:* Re: namenode could not start
>>
>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>> right permission?
>>
>>
>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>
>>> Dear all:
>>>
>>> I had a problem that the namenode could not start when i ran
>>> start-dfs.sh . Show the message as below:
>>>
>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>> namenode join
>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>> storage directory does not exist or is not accessible.
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>
>>> Thank for any help
>>>
>>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
Yes.But the issue has been fixed, thanks for help.
in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
format"
On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> are you getting same exception..? If do format and then start-dfs.sh..
>
>
>
> are you using the same config..? I mean, while formatting the namenodeand while starting..
>
>
>
> can you please check or paste the configurations,exceptions in namenodelog and format log..
>
>
>
> and hope you are formatting and starting with same user..
>
>
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* haihong lu [ung3210@gmail.com]
> *Sent:* Wednesday, March 26, 2014 7:04 AM
> *To:* user
>
> *Subject:* Re: namenode could not start
>
> /home/hadoop/mydata/hdfs/namenode should be created when executed
> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
> effect.
>
>
> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> Please format the namenode and then do start-dfs..
>>
>>
>>
>>
>>
>> *Command for namenode format:*
>>
>>
>>
>> hdfs namenode -format
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>> *To:* user@hadoop.apache.org
>> *Subject:* Re: namenode could not start
>>
>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>> right permission?
>>
>>
>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>
>>> Dear all:
>>>
>>> I had a problem that the namenode could not start when i ran
>>> start-dfs.sh . Show the message as below:
>>>
>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>> namenode join
>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>> storage directory does not exist or is not accessible.
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>
>>> Thank for any help
>>>
>>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
Yes.But the issue has been fixed, thanks for help.
in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
format"
On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> are you getting same exception..? If do format and then start-dfs.sh..
>
>
>
> are you using the same config..? I mean, while formatting the namenodeand while starting..
>
>
>
> can you please check or paste the configurations,exceptions in namenodelog and format log..
>
>
>
> and hope you are formatting and starting with same user..
>
>
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* haihong lu [ung3210@gmail.com]
> *Sent:* Wednesday, March 26, 2014 7:04 AM
> *To:* user
>
> *Subject:* Re: namenode could not start
>
> /home/hadoop/mydata/hdfs/namenode should be created when executed
> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
> effect.
>
>
> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> Please format the namenode and then do start-dfs..
>>
>>
>>
>>
>>
>> *Command for namenode format:*
>>
>>
>>
>> hdfs namenode -format
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>> *To:* user@hadoop.apache.org
>> *Subject:* Re: namenode could not start
>>
>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>> right permission?
>>
>>
>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>
>>> Dear all:
>>>
>>> I had a problem that the namenode could not start when i ran
>>> start-dfs.sh . Show the message as below:
>>>
>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>> namenode join
>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>> storage directory does not exist or is not accessible.
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>
>>> Thank for any help
>>>
>>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
Yes.But the issue has been fixed, thanks for help.
in myscript, i used "hdfs namenode -format" instead of "hdfs namenode
format"
On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> are you getting same exception..? If do format and then start-dfs.sh..
>
>
>
> are you using the same config..? I mean, while formatting the namenodeand while starting..
>
>
>
> can you please check or paste the configurations,exceptions in namenodelog and format log..
>
>
>
> and hope you are formatting and starting with same user..
>
>
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* haihong lu [ung3210@gmail.com]
> *Sent:* Wednesday, March 26, 2014 7:04 AM
> *To:* user
>
> *Subject:* Re: namenode could not start
>
> /home/hadoop/mydata/hdfs/namenode should be created when executed
> start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
> effect.
>
>
> On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
> brahmareddy.battula@huawei.com> wrote:
>
>> Please format the namenode and then do start-dfs..
>>
>>
>>
>>
>>
>> *Command for namenode format:*
>>
>>
>>
>> hdfs namenode -format
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards
>>
>>
>>
>> Brahma Reddy Battula
>>
>>
>> ------------------------------
>> *From:* Azuryy Yu [azuryyyu@gmail.com]
>> *Sent:* Tuesday, March 25, 2014 2:39 PM
>> *To:* user@hadoop.apache.org
>> *Subject:* Re: namenode could not start
>>
>> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a
>> right permission?
>>
>>
>> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>>
>>> Dear all:
>>>
>>> I had a problem that the namenode could not start when i ran
>>> start-dfs.sh . Show the message as below:
>>>
>>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>>> namenode join
>>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>>> storage directory does not exist or is not accessible.
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>>
>>> Thank for any help
>>>
>>>
>>
>
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
are you getting same exception..? If do format and then start-dfs.sh..
are you using the same config..? I mean, while formatting the namenode and while starting..
can you please check or paste the configurations,exceptions in namenode log and format log..
and hope you are formatting and starting with same user..
Thanks & Regards
Brahma Reddy Battula
________________________________
From: haihong lu [ung3210@gmail.com]
Sent: Wednesday, March 26, 2014 7:04 AM
To: user
Subject: Re: namenode could not start
/home/hadoop/mydata/hdfs/namenode should be created when executed start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <br...@huawei.com>> wrote:
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com<ma...@gmail.com>]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
are you getting same exception..? If do format and then start-dfs.sh..
are you using the same config..? I mean, while formatting the namenode and while starting..
can you please check or paste the configurations,exceptions in namenode log and format log..
and hope you are formatting and starting with same user..
Thanks & Regards
Brahma Reddy Battula
________________________________
From: haihong lu [ung3210@gmail.com]
Sent: Wednesday, March 26, 2014 7:04 AM
To: user
Subject: Re: namenode could not start
/home/hadoop/mydata/hdfs/namenode should be created when executed start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <br...@huawei.com>> wrote:
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com<ma...@gmail.com>]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
are you getting same exception..? If do format and then start-dfs.sh..
are you using the same config..? I mean, while formatting the namenode and while starting..
can you please check or paste the configurations,exceptions in namenode log and format log..
and hope you are formatting and starting with same user..
Thanks & Regards
Brahma Reddy Battula
________________________________
From: haihong lu [ung3210@gmail.com]
Sent: Wednesday, March 26, 2014 7:04 AM
To: user
Subject: Re: namenode could not start
/home/hadoop/mydata/hdfs/namenode should be created when executed start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <br...@huawei.com>> wrote:
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com<ma...@gmail.com>]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
are you getting same exception..? If do format and then start-dfs.sh..
are you using the same config..? I mean, while formatting the namenode and while starting..
can you please check or paste the configurations,exceptions in namenode log and format log..
and hope you are formatting and starting with same user..
Thanks & Regards
Brahma Reddy Battula
________________________________
From: haihong lu [ung3210@gmail.com]
Sent: Wednesday, March 26, 2014 7:04 AM
To: user
Subject: Re: namenode could not start
/home/hadoop/mydata/hdfs/namenode should be created when executed start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <br...@huawei.com>> wrote:
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com<ma...@gmail.com>]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org<ma...@hadoop.apache.org>
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
/home/hadoop/mydata/hdfs/namenode should be created when executed
start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> Please format the namenode and then do start-dfs..
>
>
>
>
>
> *Command for namenode format:*
>
>
>
> hdfs namenode -format
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* Azuryy Yu [azuryyyu@gmail.com]
> *Sent:* Tuesday, March 25, 2014 2:39 PM
> *To:* user@hadoop.apache.org
> *Subject:* Re: namenode could not start
>
> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
> permission?
>
>
> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>
>> Dear all:
>>
>> I had a problem that the namenode could not start when i ran start-dfs.sh
>> . Show the message as below:
>>
>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>> namenode join
>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>> storage directory does not exist or is not accessible.
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>
>> Thank for any help
>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
/home/hadoop/mydata/hdfs/namenode should be created when executed
start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> Please format the namenode and then do start-dfs..
>
>
>
>
>
> *Command for namenode format:*
>
>
>
> hdfs namenode -format
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* Azuryy Yu [azuryyyu@gmail.com]
> *Sent:* Tuesday, March 25, 2014 2:39 PM
> *To:* user@hadoop.apache.org
> *Subject:* Re: namenode could not start
>
> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
> permission?
>
>
> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>
>> Dear all:
>>
>> I had a problem that the namenode could not start when i ran start-dfs.sh
>> . Show the message as below:
>>
>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>> namenode join
>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>> storage directory does not exist or is not accessible.
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>
>> Thank for any help
>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
/home/hadoop/mydata/hdfs/namenode should be created when executed
start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> Please format the namenode and then do start-dfs..
>
>
>
>
>
> *Command for namenode format:*
>
>
>
> hdfs namenode -format
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* Azuryy Yu [azuryyyu@gmail.com]
> *Sent:* Tuesday, March 25, 2014 2:39 PM
> *To:* user@hadoop.apache.org
> *Subject:* Re: namenode could not start
>
> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
> permission?
>
>
> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>
>> Dear all:
>>
>> I had a problem that the namenode could not start when i ran start-dfs.sh
>> . Show the message as below:
>>
>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>> namenode join
>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>> storage directory does not exist or is not accessible.
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>
>> Thank for any help
>>
>>
>
Re: namenode could not start
Posted by haihong lu <un...@gmail.com>.
/home/hadoop/mydata/hdfs/namenode should be created when executed
start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no
effect.
On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula <
brahmareddy.battula@huawei.com> wrote:
> Please format the namenode and then do start-dfs..
>
>
>
>
>
> *Command for namenode format:*
>
>
>
> hdfs namenode -format
>
>
>
>
>
>
>
> Thanks & Regards
>
>
>
> Brahma Reddy Battula
>
>
> ------------------------------
> *From:* Azuryy Yu [azuryyyu@gmail.com]
> *Sent:* Tuesday, March 25, 2014 2:39 PM
> *To:* user@hadoop.apache.org
> *Subject:* Re: namenode could not start
>
> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
> permission?
>
>
> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
>
>> Dear all:
>>
>> I had a problem that the namenode could not start when i ran start-dfs.sh
>> . Show the message as below:
>>
>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
>> namenode join
>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
>> storage directory does not exist or is not accessible.
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>>
>> Thank for any help
>>
>>
>
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
RE: namenode could not start
Posted by Brahma Reddy Battula <br...@huawei.com>.
Please format the namenode and then do start-dfs..
Command for namenode format:
hdfs namenode -format
Thanks & Regards
Brahma Reddy Battula
________________________________
From: Azuryy Yu [azuryyyu@gmail.com]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user@hadoop.apache.org
Subject: Re: namenode could not start
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com>> wrote:
Dear all:
I had a problem that the namenode could not start when i ran start-dfs.sh . Show the message as below:
FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
Thank for any help
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
> Dear all:
>
> I had a problem that the namenode could not start when i ran start-dfs.sh
> . Show the message as below:
>
> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
> namenode join
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
> storage directory does not exist or is not accessible.
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>
> Thank for any help
>
>
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
> Dear all:
>
> I had a problem that the namenode could not start when i ran start-dfs.sh
> . Show the message as below:
>
> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
> namenode join
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
> storage directory does not exist or is not accessible.
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>
> Thank for any help
>
>
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
> Dear all:
>
> I had a problem that the namenode could not start when i ran start-dfs.sh
> . Show the message as below:
>
> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
> namenode join
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
> storage directory does not exist or is not accessible.
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>
> Thank for any help
>
>
Re: namenode could not start
Posted by Azuryy Yu <az...@gmail.com>.
Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a right
permission?
On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <un...@gmail.com> wrote:
> Dear all:
>
> I had a problem that the namenode could not start when i ran start-dfs.sh
> . Show the message as below:
>
> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in
> namenode join
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state:
> storage directory does not exist or is not accessible.
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
>
> Thank for any help
>
>