[
https://issues.apache.org/jira/browse/HDFS-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245981#comment-13245981
]
Aaron T. Myers commented on HDFS-3102:
--------------------------------------
I should also mention that I tested this manually by:
# Formatting an HA NN.
# Removing the shared dir.
# Confirming the NN wouldn't start.
# Running `hdfs namenode -initializeSharedEdits' on that NN.
# Confirming that the NN would start.
# Transitioning the NN to active.
# Running `hdfs namenode -bootstrapStandby' on the other NN.
# Starting the second NN.
# Confirming that failovers could proceed back and forth between the two NNs.
> Add CLI tool to initialize the shared-edits dir
> -----------------------------------------------
>
> Key: HDFS-3102
> URL: https://issues.apache.org/jira/browse/HDFS-3102
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha, name-node
> Affects Versions: 0.24.0, 2.0.0
> Reporter: Todd Lipcon
> Assignee: Aaron T. Myers
> Attachments: HDFS-3102.patch
>
>
> Currently in order to make a non-HA NN HA, you need to initialize the shared
> edits dir. This can be done manually by cping directories around. It would be
> preferable to add a "namenode -initializeSharedEdits" command to achieve this
> same effect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
