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 "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2010/03/16 00:58:27 UTC
[jira] Created: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
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
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.
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869421#action_12869421 ]
Hudson commented on HADOOP-6633:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #258 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/258/])
HADOOP-6633. normalize property names for JT/NN kerberos principal names in configuration
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Updated: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6633:
-----------------------------------
Attachment: HADOOP-6633-BP20.patch
for previous version, not for commit.
> 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.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.
[jira] Updated: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6633:
-----------------------------------
Attachment: HADOOP-6633-BP20-1.patch
added changes to proxyuser keys.
"hadoop.proxyuser."+userName+".ip-addresses and
"hadoop.proxyuser."+userName+".users"
> 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.
[jira] Updated: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6633:
-----------------------------------
Attachment: HADOOP-6633-BP20-2.patch
addressed Allen's comment. 'principal' makes more sense.
> 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-2.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.
[jira] Updated: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6633:
-----------------------------------
Attachment: HADOOP-6633.patch
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Updated: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-6633:
--------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
Resolving.
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868938#action_12868938 ]
Hadoop QA commented on HADOOP-6633:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12444862/HADOOP-6633.patch
against trunk revision 945953.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/529/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/529/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/529/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/529/console
This message is automatically generated.
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846449#action_12846449 ]
Boris Shkolnik commented on HADOOP-6633:
----------------------------------------
to summarize keys changes:
hdfs-site.xml
"dfs.namenode.user.name" to "dfs.namenode.kerberos.principal";
"dfs.namenode.https.user.name" to "dfs.namenode.kerberos.https.principal"
"dfs.secondary.namenode.user.name" to "dfs.secondary.namenode.kerberos.principal";
"dfs.secondary.namenode.https.user.name" to "dfs.secondary.namenode.kerberos.https.principal";
"dfs.datanode.user.name" to "dfs.datanode.kerberos.principal"
mapred-site.xml
"mapreduce.jobtracker.user.name" to "mapreduce.jobtracker.kerberos.principal";
"mapreduce.tasktracker.user.name" to "mapreduce.tasktracker.kerberos.principal"
superuser stuff:
"hadoop.proxyuser."userName".ip-addresses to "hadoop.proxyuser."userName".hosts
"hadoop.proxyuser."userName".users" to "hadoop.proxyuser."userName".groups"
> 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-2.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.
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871317#action_12871317 ]
Hudson commented on HADOOP-6633:
--------------------------------
Integrated in Hadoop-Common-trunk #346 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/346/])
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Assigned: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik reassigned HADOOP-6633:
--------------------------------------
Assignee: Boris Shkolnik
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.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.
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869376#action_12869376 ]
Jitendra Nath Pandey commented on HADOOP-6633:
----------------------------------------------
+1 for the patch.
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Updated: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6633:
-----------------------------------
Status: Patch Available (was: Open)
> 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
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6633-BP20-1.patch, HADOOP-6633-BP20-2.patch, HADOOP-6633-BP20.patch, HADOOP-6633.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.
[jira] Commented: (HADOOP-6633) normalize property names for JT/NN
kerberos principal names in configuration
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ 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.