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

Todd Lipcon commented on HDFS-2819:
-----------------------------------

{code}
+    often the logs are rolled. Note that failover triggers a log roll
+    so the StandbyNode quickly becomes up-to-date.
{code}
I think better to say "so the StandbyNode will always be up to date before it 
becomes Active>'
----
- I think dfs.ha.standby.checkpoints can be left undocumented - I only added it 
for testing purposes, but I can't think of any reason why you wouldn't want it 
(it's currently the only way to do checkpoints in HA!)

- I don't follow why dfs.ha.fencing.methods, 
dfs.ha.fencing.ssh.private-key-files, dfs.federation.nameservices, etc aren't 
documented in -default. It's OK to have them there with a blank 
<value></value>. I agree that the ones that are just prefixes (eg 
dfs.ha.namenodes) need to be documented elsewhere, unless you put them there as 
"dfs.ha.namenodes.EXAMPLENAMESERVICE".

                
> Document new HA-related configs in hdfs-default.xml
> ---------------------------------------------------
>
>                 Key: HDFS-2819
>                 URL: https://issues.apache.org/jira/browse/HDFS-2819
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: documentation, ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Eli Collins
>         Attachments: hdfs-2819.txt, hdfs-2819.txt
>
>
> We've added a few configs, like shared edits dir, dfs.ha.namenodes, etc - we 
> should probably add these to hdfs-default.xml so they get documented.

--
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