[
https://issues.apache.org/jira/browse/HDFS-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HDFS-2934.
-------------------------------
Resolution: Fixed
Fix Version/s: HA branch (HDFS-1623)
Hadoop Flags: Reviewed
Thanks for the review. I addressed the nits on commit.
> HA: Allow configs to be scoped to all NNs in the nameservice
> ------------------------------------------------------------
>
> Key: HDFS-2934
> URL: https://issues.apache.org/jira/browse/HDFS-2934
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: HA branch (HDFS-1623)
>
> Attachments: hdfs-2934.txt
>
>
> Currently, for namenode-specific keys in HA, one must configure them as
> keyfoo.nameserviceid.namenodeid. However, in many cases all of the NNs in a
> nameservice would share the same value. So we should allow the configuration
> of "keyfoo.nameserviceid" to apply to all NNs. The resolution path for these
> keys would then be:
> keyfoo.nameserviceid.nnid
> keyfoo.nameserviceid (if above not set)
> keyfoo (if neither of above set)
--
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
