[
https://issues.apache.org/jira/browse/HDFS-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-2733:
---------------------------------
Attachment: HDFSHighAvailability.html
HDFS-2733-HDFS-1623.patch
Thanks a lot for the review, Eli. Here's a patch which addresses all of your
feedback, except for the following:
bq. Perhaps be explicit that there are two types of state, persistent and
ephemeral state. That all persistent state modifications and some emphemeral
(eg block allocation) are logged, with the remaining ephemeral state (block
reports) are handled by the Datanodes communicating two both Namenodes.
bq. Might be worth mentioning that we fence both with the fencers but the NNs
also fence operations outside the edits log (eg operations from block reports)
Both of these facts seem more developer-oriented to me, and not particularly
pertinent to operators. I think adding this material would only serve to
confuse operators, and add little value.
bq. Wrt syncing metadata directories, perhaps worth noting that you only need
to sync the edits directory since the shared edits dir only contains edits
(people may be confused why the old image they copied there never gets updated)
I already do say that you should copy over the fsimage/edits to the second
NameNode, and only put the recent edits in the shared directory. What more do
you think should be said?
> Document HA configuration and CLI
> ---------------------------------
>
> Key: HDFS-2733
> URL: https://issues.apache.org/jira/browse/HDFS-2733
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: documentation, ha
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Aaron T. Myers
> Attachments: HDFS-2733-HDFS-1623.patch, HDFS-2733-HDFS-1623.patch,
> HDFS-2733-HDFS-1623.patch, HDFSHighAvailability.html,
> HDFSHighAvailability.html, HDFSHighAvailability.html
>
>
> We need to document the configuration changes in HDFS-2231 and the new CLI
> introduced by HADOOP-7774.
--
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
