Scribd Logo
Upload

Welcome to Scribd!

  • Recovering Namenode From Secondarynamenode

    Uploaded by

    sairamgopal
    18 views1 page
    1. Stop the existing Hadoop cluster and format a new NameNode on a separate machine. 2. Copy the fsimage file from the Secondary NameNode's checkpoint directory to the new NameNode's filesystem directory. 3. Start the new NameNode with the "-upgrade" option to recover the filesystem metadata from the copied fsimage file and safely start the Hadoop cluster.

    Original Description:

    name node recovery

    Original Title

    Namenode Recovery

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    1. Stop the existing Hadoop cluster and format a new NameNode on a separate machine. 2. Copy the fsimage file from the Secondary NameNode's checkpoint directory to the new NameNode's filesystem directory. 3. Start the new NameNode with the "-upgrade" option to recover the filesystem metadata from the copied fsimage file and safely start the Hadoop cluster.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    18 views1 page

    Recovering Namenode From Secondarynamenode

    Uploaded by

    sairamgopal
    1. Stop the existing Hadoop cluster and format a new NameNode on a separate machine. 2. Copy the fsimage file from the Secondary NameNode's checkpoint directory to the new NameNode's filesystem directory. 3. Start the new NameNode with the "-upgrade" option to recover the filesystem metadata from the copied fsimage file and safely start the Hadoop cluster.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 1

    Recovering namenode from secondarynamenode

    ======================================================================
    Recovering namenode by start from another machine
    ======================================================================
    -----------------------------------------------------------------------------------------------------------1. Stop the cluster to make sure all data-nodes and job/task-tracker are down.
    (Eg, bin/stop-all.sh)
    -----------------------------------------------------------------------------------------------------------2. Select a node where you will run a new name-node, and set it up as usually for the name-node.
    --------------------------------------------------------------------------------------------- --------------3. Format the new name-node.
    (Eg, bin/hadoop namenode -format)
    -----------------------------------------------------------------------------------------------------------4. cd <dfs.name.dir>/current
    -----------------------------------------------------------------------------------------------------------5. You will see file VERSION in there. You will need to provide namespaceID of the old cluster in it.
    -----------------------------------------------------------------------------------------------------------6. The old namespaceID could be obtained from one of the data-nodes.
    --------------------------------------------------------------------------------------------------------7. just copy it from <dfs.data.dir>/current/VERSION.namespaceID
    --------------------------------------------------------------------------------------------------------8. In the New machine(Namenode) rm <dfs.name.dir>/current/fsimage
    (Eg, rm -r /hadoop/hdfs/current/fsimage)
    --------------------------------------------------------------------------------------------------------9. In the namenode scp <secondary-node>:<fs.checkpoint.dir>/fsimage ./fsimage
    (Eg, scp /hadoop/snn/checkpoint/current/fsimage NewNamenode:/hadoop/hdfs/name/current/)
    --------------------------------------------------------------------------------------------------------10. Start the cluster. Upgrade is recommended, so that you could rollback if something goes wrong.
    (Eg, bin/hadoop namenode -upgrade)
    --------------------------------------------------------------------------------------------------------11. Run fsck, and remove files with missing blocks if any

    You might also like