[ 
https://issues.apache.org/jira/browse/HDFS-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201513#comment-13201513
 ] 

Todd Lipcon commented on HDFS-2733:
-----------------------------------

- "In the event of an unplanned event" could be worded better
- The doc for dfs.federation.nameservices should indicate that, if federation 
is also being used, that this would be a comma-separated list of nameservice 
IDs (some of which may be HA and some of which might not be)
- I think the example nameservice ID should be something like "mycluster" or 
"mynameservice" rather than "ha-nn-uri" -- it doubles as the URI but that's a 
side effect rather than the important bit, I think.
- Add a "note" for dfs.namenode.http-address that https-address should be 
configured on a secure cluster
- For the "shell" fencing method, should note that the address of the service 
to be fenced will be inserted as the first argument
- "This is not yet implemented, and at present will always return success" -- 
if the NN is down it will return non-zero, right? So it still has some basic 
use.

                
> 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, HDFS-2733-HDFS-1623.patch, 
> HDFS-2733-HDFS-1623.patch, HDFSHighAvailability.html, 
> HDFSHighAvailability.html, 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

        

Reply via email to