FAQ
I used the manager to start CDH4 with one cluster on three servers.


The service hdfs1 has status Started but with Health Bad. The Role Countes
are 1 SecondaryNameNode, 1 NameNode, 1 Balancer, 2 DataNodes.
Further drill down it indicated the NameNode is Bad. The log has 2 warnings
and 1 fatal error.


My questions are:

1. How to fix the warnings? What are the suggested directory values?

2. How to fix the fatal error - NameNode not formated.

3. Should I be expecting 3 DataNodes? How can I add the third DataNode?
Warning: Only one dfs.namenode.name.dir directory configured , beware data
loss!
Warning: Only one dfs.namenode.edits.dir directory configured , beware data
loss!
Error: Exception in namenode join
java.io.IOException: NameNode is not formatted.
  at
org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
  at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
  at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
  at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
  at
org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
  at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
  at
org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:571)
  at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
  at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)

Search Discussions

  • Adam Smieszny at Aug 15, 2012 at 10:24 pm
    Hi Jghuan,

    The issue shows up in your logs here:
    Error: Exception in namenode join
    *java.io.IOException: NameNode is not formatted.*

    Typically, Cloudera Manager will format the NN for you as you progress
    through the setup "wizard" - did you skip ahead to the main services screen
    prior to that step?

    Regardless, you should be fine if you do the following:
    1) From main services screen, ensure that you deploy client configuration
    from the Actions button
    2) Shut down your hadoop services via Manager
    2) On any of the machines, run a 'hadoop namenode -format'
    3) Start the services via Manager

    Hope this helps
    Thanks,
    Adam
    On Wed, Aug 15, 2012 at 5:44 PM, jghuang wrote:

    I used the manager to start CDH4 with one cluster on three servers.
    ******

    The service hdfs1 has status Started but with Health Bad. The Role Countes
    are 1 SecondaryNameNode, 1 NameNode, 1 Balancer, 2 DataNodes.****
    Further drill down it indicated the NameNode is Bad. The log has 2
    warnings and 1 fatal error.
    ****

    My questions are:****

    1. How to fix the warnings? What are the suggested directory values?****

    2. How to fix the fatal error - NameNode not formated.****

    3. Should I be expecting 3 DataNodes? How can I add the third DataNode?***
    *
    Warning: Only one dfs.namenode.name.dir directory configured , beware data
    loss!
    Warning: Only one dfs.namenode.edits.dir directory configured , beware
    data loss!
    Error: Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at
    org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny
  • Adam Smieszny at Aug 15, 2012 at 10:34 pm
    Argh, sorry, hit reply before I responded to the other two questions:

    My questions are:****

    1. How to fix the warnings? What are the suggested directory values?****

    We do suggest that you write to multiple disks for extra reliability, for
    the two parameters you see there.

    For instance, if you have two disks mounted in your namenode at mount
    points /data1 and /data2

    set dfs.namenode.name.dir to /data1/nn,/data2/nn

    We would also suggest that a third location be on an NFS mount, for a
    physically separate copy of the data

    The same goes for the other.


    3. Should I be expecting 3 DataNodes? How can I add the third DataNode?
    What is the purpose of this cluster? Typically, you want your namenode
    running on a separate machine from any datanodes, so you would only have
    1NN and 2DN
    However, I occasionally run NN and DN processes on same machine. Cloudera
    Manager makes it easy to add new services (such as DN) to existing hosts in
    the cluster - go in to HDFS -> Instances -> Add Role

    Hope this helps,
    Adam

    On Wed, Aug 15, 2012 at 6:24 PM, Adam Smieszny wrote:

    Hi Jghuan,

    The issue shows up in your logs here:
    Error: Exception in namenode join
    *java.io.IOException: NameNode is not formatted.*

    Typically, Cloudera Manager will format the NN for you as you progress
    through the setup "wizard" - did you skip ahead to the main services screen
    prior to that step?

    Regardless, you should be fine if you do the following:
    1) From main services screen, ensure that you deploy client configuration
    from the Actions button
    2) Shut down your hadoop services via Manager
    2) On any of the machines, run a 'hadoop namenode -format'
    3) Start the services via Manager

    Hope this helps
    Thanks,
    Adam
    On Wed, Aug 15, 2012 at 5:44 PM, jghuang wrote:

    I used the manager to start CDH4 with one cluster on three servers.
    ******

    The service hdfs1 has status Started but with Health Bad. The Role
    Countes are 1 SecondaryNameNode, 1 NameNode, 1 Balancer, 2 DataNodes.****
    Further drill down it indicated the NameNode is Bad. The log has 2
    warnings and 1 fatal error.
    ****

    My questions are:****

    1. How to fix the warnings? What are the suggested directory values?****

    2. How to fix the fatal error - NameNode not formated.****

    3. Should I be expecting 3 DataNodes? How can I add the third DataNode?**
    **
    Warning: Only one dfs.namenode.name.dir directory configured , beware
    data loss!
    Warning: Only one dfs.namenode.edits.dir directory configured , beware
    data loss!
    Error: Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at
    org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny

    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny
  • Jghuang at Aug 16, 2012 at 4:07 pm
    I didn't skip any steps but I might have accidentally wiped out the default
    directory.

    I might have done something wrong here. I folowed your instruction below.
    When deploy the client configuration I received the folowing under Child
    Commands for both mapreduce1 and hdfs both said Command completed with 1/2
    success.

    I proceeded to Stop hdfs and run hadoop namenode -format (it said the
    command is deprecated, btw). I entered Y at the "Re-format filesystem in
    /tmp/hadoop-root/dfs/name" prompt and successfully ran it.

    But after I started the services, I got the "Command
    'HdfsStartWithFailovers' failed for service 'hdfs1'" still receiverror.
    From the log of the NameNode it looks like the same error:
      August 16 2012 11:58 AM ERROR
    org.apache.hadoop.hdfs.server.namenode.NameNode

    Exception in namenode join
    java.io.IOException: NameNode is not formatted.
      at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
      at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
      at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
      at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:571)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)



    On Wednesday, August 15, 2012 6:24:03 PM UTC-4, Adam Smieszny wrote:

    Hi Jghuan,

    The issue shows up in your logs here:
    Error: Exception in namenode join
    *java.io.IOException: NameNode is not formatted.*

    Typically, Cloudera Manager will format the NN for you as you progress
    through the setup "wizard" - did you skip ahead to the main services screen
    prior to that step?

    Regardless, you should be fine if you do the following:
    1) From main services screen, ensure that you deploy client configuration
    from the Actions button
    2) Shut down your hadoop services via Manager
    2) On any of the machines, run a 'hadoop namenode -format'
    3) Start the services via Manager

    Hope this helps
    Thanks,
    Adam

    On Wed, Aug 15, 2012 at 5:44 PM, jghuang <jhu...@tervela.com <javascript:>
    wrote:
    I used the manager to start CDH4 with one cluster on three servers.
    ******

    The service hdfs1 has status Started but with Health Bad. The Role
    Countes are 1 SecondaryNameNode, 1 NameNode, 1 Balancer, 2 DataNodes.****
    Further drill down it indicated the NameNode is Bad. The log has 2
    warnings and 1 fatal error.
    ****

    My questions are:****

    1. How to fix the warnings? What are the suggested directory values?****

    2. How to fix the fatal error - NameNode not formated.****

    3. Should I be expecting 3 DataNodes? How can I add the third DataNode?**
    **
    Warning: Only one dfs.namenode.name.dir directory configured , beware
    data loss!
    Warning: Only one dfs.namenode.edits.dir directory configured , beware
    data loss!
    Error: Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at
    org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny
  • Jghuang at Aug 16, 2012 at 4:30 pm
    Arrr, some user error. I no longer have the Command completed with 1/2
    success.

    But after I started the service I still get the following errors:

    Command 'HdfsStartWithFailovers' failed for service 'hdfs1'



    Command 'Start' failed for service 'hdfs1'



    and the same error:



    August 16 2012 12:27 PMERRORorg.apache.hadoop.hdfs.server.namenode.NameNode

    Exception in namenode join
    java.io.IOException: NameNode is not formatted.
      at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
      at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
      at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
      at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:571)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
      at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)

    On Thursday, August 16, 2012 12:07:35 PM UTC-4, jghuang wrote:

    I didn't skip any steps but I might have accidentally wiped out the
    default directory.

    I might have done something wrong here. I folowed your instruction below.
    When deploy the client configuration I received the folowing under Child
    Commands for both mapreduce1 and hdfs both said Command completed with 1/2
    success.

    I proceeded to Stop hdfs and run hadoop namenode -format (it said the
    command is deprecated, btw). I entered Y at the "Re-format filesystem in
    /tmp/hadoop-root/dfs/name" prompt and successfully ran it.

    But after I started the services, I got the "Command
    'HdfsStartWithFailovers' failed for service 'hdfs1'" still receiverror.
    From the log of the NameNode it looks like the same error:
    August 16 2012 11:58 AM ERROR
    org.apache.hadoop.hdfs.server.namenode.NameNode

    Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)



    On Wednesday, August 15, 2012 6:24:03 PM UTC-4, Adam Smieszny wrote:

    Hi Jghuan,

    The issue shows up in your logs here:
    Error: Exception in namenode join
    *java.io.IOException: NameNode is not formatted.*

    Typically, Cloudera Manager will format the NN for you as you progress
    through the setup "wizard" - did you skip ahead to the main services screen
    prior to that step?

    Regardless, you should be fine if you do the following:
    1) From main services screen, ensure that you deploy client configuration
    from the Actions button
    2) Shut down your hadoop services via Manager
    2) On any of the machines, run a 'hadoop namenode -format'
    3) Start the services via Manager

    Hope this helps
    Thanks,
    Adam
    On Wed, Aug 15, 2012 at 5:44 PM, jghuang wrote:

    I used the manager to start CDH4 with one cluster on three servers.
    ******

    The service hdfs1 has status Started but with Health Bad. The Role
    Countes are 1 SecondaryNameNode, 1 NameNode, 1 Balancer, 2 DataNodes.***
    *
    Further drill down it indicated the NameNode is Bad. The log has 2
    warnings and 1 fatal error.
    ****

    My questions are:****

    1. How to fix the warnings? What are the suggested directory values?****

    2. How to fix the fatal error - NameNode not formated.****

    3. Should I be expecting 3 DataNodes? How can I add the third DataNode?*
    ***
    Warning: Only one dfs.namenode.name.dir directory configured , beware
    data loss!
    Warning: Only one dfs.namenode.edits.dir directory configured , beware
    data loss!
    Error: Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at
    org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
    at
    org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
    at
    org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/about
    917.830.4156 | http://www.linkedin.com/in/adamsmieszny
  • Joey Echeverria at Aug 16, 2012 at 4:58 pm
    Did you format using the command in the CM GUI as adam described?

    -Joey
    On Thu, Aug 16, 2012 at 12:30 PM, jghuang wrote:

    Arrr, some user error. I no longer have the Command completed with 1/2
    success.

    But after I started the service I still get the following errors:

    Command 'HdfsStartWithFailovers' failed for service 'hdfs1'



    Command 'Start' failed for service 'hdfs1'



    and the same error:



    August 16 2012 12:27 PMERRORorg.apache.hadoop.hdfs.server.namenode.NameNode

    Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:190)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:354)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:389)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:423)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:590)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:571)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1134)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)

    On Thursday, August 16, 2012 12:07:35 PM UTC-4, jghuang wrote:

    I didn't skip any steps but I might have accidentally wiped out the
    default directory.

    I might have done something wrong here. I folowed your instruction below.
    When deploy the client configuration I received the folowing under Child
    Commands for both mapreduce1 and hdfs both said Command completed with 1/2
    success.

    I proceeded to Stop hdfs and run hadoop namenode -format (it said the
    command is deprecated, btw). I entered Y at the "Re-format filesystem in
    /tmp/hadoop-root/dfs/name" prompt and successfully ran it.

    But after I started the services, I got the "Command
    'HdfsStartWithFailovers' failed for service 'hdfs1'" still receiverror.
    From the log of the NameNode it looks like the same error:
    August 16 2012 11:58 AM ERROR org.apache.hadoop.hdfs.server.**
    namenode.NameNode

    Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at org.apache.hadoop.hdfs.server.**namenode.FSImage.**recoverTransitionRead(FSImage.**java:190)
    at org.apache.hadoop.hdfs.server.**namenode.FSNamesystem.**loadFSImage(FSNamesystem.java:**498)
    at org.apache.hadoop.hdfs.server.**namenode.FSNamesystem.**loadFromDisk(FSNamesystem.**java:390)
    at org.apache.hadoop.hdfs.server.**namenode.FSNamesystem.**loadFromDisk(FSNamesystem.**java:354)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.**loadNamesystem(NameNode.java:**389)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.initialize(**NameNode.java:423)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.<init>(**NameNode.java:590)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.<init>(**NameNode.java:571)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.**createNameNode(NameNode.java:**1134)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.main(**NameNode.java:1193)



    On Wednesday, August 15, 2012 6:24:03 PM UTC-4, Adam Smieszny wrote:

    Hi Jghuan,

    The issue shows up in your logs here:
    Error: Exception in namenode join
    *java.io.IOException: NameNode is not formatted.*

    Typically, Cloudera Manager will format the NN for you as you progress
    through the setup "wizard" - did you skip ahead to the main services screen
    prior to that step?

    Regardless, you should be fine if you do the following:
    1) From main services screen, ensure that you deploy client
    configuration from the Actions button
    2) Shut down your hadoop services via Manager
    2) On any of the machines, run a 'hadoop namenode -format'
    3) Start the services via Manager

    Hope this helps
    Thanks,
    Adam
    On Wed, Aug 15, 2012 at 5:44 PM, jghuang wrote:

    I used the manager to start CDH4 with one cluster on three servers.
    ******

    The service hdfs1 has status Started but with Health Bad. The Role
    Countes are 1 SecondaryNameNode, 1 NameNode, 1 Balancer, 2 DataNodes.**
    **
    Further drill down it indicated the NameNode is Bad. The log has 2
    warnings and 1 fatal error.
    ****

    My questions are:****

    1. How to fix the warnings? What are the suggested directory values?***
    *

    2. How to fix the fatal error - NameNode not formated.****

    3. Should I be expecting 3 DataNodes? How can I add the third DataNode?
    ****
    Warning: Only one dfs.namenode.name.dir directory configured , beware
    data loss!
    Warning: Only one dfs.namenode.edits.dir directory configured , beware
    data loss!
    Error: Exception in namenode join
    java.io.IOException: NameNode is not formatted.
    at org.apache.hadoop.hdfs.server.**namenode.FSImage.**
    recoverTransitionRead(FSImage.**java:190)
    at org.apache.hadoop.hdfs.server.**namenode.FSNamesystem.**
    loadFSImage(FSNamesystem.java:**498)
    at org.apache.hadoop.hdfs.server.**namenode.FSNamesystem.**
    loadFromDisk(FSNamesystem.**java:390)
    at org.apache.hadoop.hdfs.server.**namenode.FSNamesystem.**
    loadFromDisk(FSNamesystem.**java:354)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.**
    loadNamesystem(NameNode.java:**389)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.initialize(**
    NameNode.java:423)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.<init>(**
    NameNode.java:590)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.<init>(**
    NameNode.java:571)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.**
    createNameNode(NameNode.java:**1134)
    at org.apache.hadoop.hdfs.server.**namenode.NameNode.main(**
    NameNode.java:1193)


    --
    Adam Smieszny
    Cloudera | Systems Engineer | http://tiny.cloudera.com/**about<http://tiny.cloudera.com/about>
    917.830.4156 | http://www.linkedin.com/in/**adamsmieszny<http://www.linkedin.com/in/adamsmieszny>

    --
    Joey Echeverria
    Principal Solutions Architect
    Cloudera, Inc.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedAug 15, '12 at 9:44p
activeAug 16, '12 at 4:58p
posts6
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase