[
https://issues.apache.org/jira/browse/HDFS-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HDFS-2819:
------------------------------
Attachment: hdfs-2819.txt
Patch attached.
- Removes "namenode" from common keys for consistency
- Does not include {{dfs.ha.allow.stale.reads}}, whether the StandbyNode allows
read operations, since this is currently only used for testing purposes.
The configuration keys w/o defaults will be documented in HDFS-2733. Here's the
list for the curious. Please chime in on HDFS-2885 if you agree we should
remove "federation" from the nameservice configs below since they may be
usedoutside federation.
{{dfs.ha.fencing.methods}} - List of fencing methods to use for service
fencing. May contain builtin methods (eg shell and sshfence) or user-defined
method.
{{dfs.ha.fencing.ssh.private-key-files}} - The SSH private key files to use
with the builtin sshfence fencer.
{{dfs.federation.nameservices}} - The list of nameservices.
{{dfs.federation.nameservice.id}} - The ID of this nameservice. If the
nameservice ID is not configured it is determined automatically by matching the
local node's address with the configured address.
{{dfs.ha.namenodes}} - The prefix for a given nameservice, lists namenodes
for a given nameservice.
{{dfs.ha.namenode.id}} - The ID of this namenode. If the namenode ID is not
configured it is determined automatically by matching the local node's address
with the configured address.
> 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
>
>
> 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
