[
https://issues.apache.org/jira/browse/HDFS-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243235#comment-13243235
]
Aaron T. Myers commented on HDFS-3164:
--------------------------------------
bq. DFS_NAMENODE_UPGRADE_PERMISSION_KEY is still used by HdfsConfiguration to
log the deprecation, so still needed, and is the only use.
But now it logs a deprecation of the key "dfs.upgrade.permission" in favor of
"dfs.namenode.upgrade.permission", which is a configuration key that's not
ready anymore. Do we have any system of deprecation which would indicate that
both of these keys are now completely unused?
> Move DatanodeInfo#hostName to DatanodeID
> ----------------------------------------
>
> Key: HDFS-3164
> URL: https://issues.apache.org/jira/browse/HDFS-3164
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-3164.txt
>
>
> Like HDFS-3138 (the ipcPort) the hostName field in DatanodeInfo is not
> ephemeral and should be in DatanodeID. This also allows us to fixup the issue
> where the DatanodeID#name field is overloaded (the DN sets it to a hostname,
> then the NN clobbers it with an IP, and then the DN clobbers it's hostname
> field with this IP). If the DN can specify both a "name" and "hostname" in
> the DatanodeID then this code becomes simpler.
--
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
