[
https://issues.apache.org/jira/browse/HDFS-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252798#comment-13252798
]
Eli Collins commented on HDFS-3159:
-----------------------------------
Looks good Todd, minor comments:
- Instructions say dfs.ha.automatic-failover.enabled is in core-site.xml,
should be hdfs-site.xml
- "notifying the other machines" / "notifying the other NameNode"
- "active node" / "active NameNode"
- "acts as a client of ZooKeeper" -> "is a ZooKeeper client"
- "has a ZKFC running on the same machine" / "has a ZKFC that runs on the same
machine as the NameNode"
- "special health-check command" / "health-check command"
- Use "local NameNode" instead of "local node" most places, eg to avoid
confusion with node in the ZK sense (eg "lock node")
- "users may refer" / "refer"
- "within 10-20 seconds", worth mentioning "ha.zookeeper.session-timeout.ms"
instead of a raw value
> Document NN auto-failover setup and configuration
> -------------------------------------------------
>
> Key: HDFS-3159
> URL: https://issues.apache.org/jira/browse/HDFS-3159
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: auto-failover, documentation, ha
> Affects Versions: Auto failover (HDFS-3042)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: HDFSHighAvailability.html, hdfs-3159.txt
>
>
> We should document how to configure, set up, and monitor an automatic
> failover setup. This will require adding the new configs to the *-default.xml
> and adding prose to the "apt" docs as well.
--
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
