[
https://issues.apache.org/jira/browse/HDFS-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-2950:
------------------------------
Resolution: Fixed
Fix Version/s: 0.23.2
0.24.0
Target Version/s: 0.24.0, 0.23.2 (was: 0.23.2, 0.24.0)
Release Note: The configuration dfs.secondary.https.port has been
renamed to dfs.namenode.secondary.https-port for consistency. The old
configuration is still supported via a deprecation path.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
> Secondary NN HTTPS address should be listed as a NAMESERVICE_SPECIFIC_KEY
> -------------------------------------------------------------------------
>
> Key: HDFS-2950
> URL: https://issues.apache.org/jira/browse/HDFS-2950
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 0.24.0, 0.23.2
>
> Attachments: hdfs-2950.txt
>
>
> This config was mistakenly left out of the NAMESERVICE_SPECIFIC_KEY map,
> which makes it tougher to configure federated clusters with security.
--
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
