hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daisuke Kobayashi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4508) Two minor improvements to the QJM Deployment docs
Date Thu, 21 Feb 2013 13:48:13 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daisuke Kobayashi updated HDFS-4508:
------------------------------------

    Attachment: HDFS-4508.patch

modified.
                
> Two minor improvements to the QJM Deployment docs
> -------------------------------------------------
>
>                 Key: HDFS-4508
>                 URL: https://issues.apache.org/jira/browse/HDFS-4508
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.0.3-alpha
>            Reporter: Harsh J
>            Assignee: Daisuke Kobayashi
>            Priority: Minor
>         Attachments: HDFS-4508.patch
>
>
> Suggested by ML user Azurry, the docs at http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/HDFSHighAvailabilityWithQJM.html#Deployment_details
can be improved for two specific lines:
> {quote}
> * If you have already formatted the NameNode, or are converting a non-HA-enabled cluster
to be HA-enabled, you should now copy over the contents of your NameNode metadata directories
to the other, unformatted NameNode by running the command "hdfs namenode -bootstrapStandby"
on the unformatted NameNode. Running this command will also ensure that the JournalNodes (as
configured by dfs.namenode.shared.edits.dir) contain sufficient edits transactions to be able
to start both NameNodes.
> * If you are converting a non-HA NameNode to be HA, you should run the command "hdfs
-initializeSharedEdits", which will initialize the JournalNodes with the edits data from the
local NameNode edits directories.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message