You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2010/03/16 18:02:27 UTC
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845997#action_12845997 ]
Allen Wittenauer commented on HADOOP-6633:
------------------------------------------
Instead of user name, shouldn't this be principal?
> normalize property names for JT/NN kerberos principal names in configuration
> ----------------------------------------------------------------------------
>
> Key: HADOOP-6633
> URL: https://issues.apache.org/jira/browse/HADOOP-6633
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20.patch
>
>
> change:
> DFS_NAMENODE_USER_NAME_KEY = "dfs.namenode.user.name" to "dfs.namenode.kerberos.user.name";
> DFS_NAMENODE_KRB_HTTPS_USER_NAME_KEY = "dfs.namenode.https.user.name" to "dfs.namenode.kerberos.https.user.name"
> DFS_SECONDARY_NAMENODE_USER_NAME_KEY = "dfs.secondary.namenode.user.name" to "dfs.secondary.namenode.kerberos.user.name";
> DFS_SECONDARY_NAMENODE_KRB_HTTPS_USER_NAME_KEY = "dfs.secondary.namenode.https.user.name" to "dfs.secondary.namenode.kerberos.https.user.name";
> DFS_DATANODE_USER_NAME_KEY = "dfs.datanode.user.name" to "dfs.datanode.kerberos.user.name"
> JT_USER_NAME = "mapreduce.jobtracker.user.name" to "mapreduce.jobtracker.kerberos.user.name";
> TT_USER_NAME = "mapreduce.tasktracker.user.name" to "mapreduce.tasktracker.kerberos.user.name"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.