hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5737) UGI checks in testcases are broken
Date Tue, 23 Mar 2010 10:17:27 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod K V updated HADOOP-5737:
------------------------------

    Release Note: Fixed a problem in the way the JobTracker used to talk to other daemons
like the NameNode to get the job's files. Also added APIs in the JobTracker to get the FileSystem
objects as per the JobTracker's configuration.  (was: Uses JobTracker's credentials for accessing
mapred.system.dir instead of using job's credentials.)

Updated release note from the commit message.

> UGI checks in testcases are broken
> ----------------------------------
>
>                 Key: HADOOP-5737
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5737
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security, test
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5737-v1.3.patch, HADOOP-5737-v1.5.patch, HADOOP-5737-v1.7.patch,
HADOOP-5737-y20.patch
>
>
> While running {{TestMiniMRWithDFSWithDistinctUsers}}, I used this patch to test the ugi
checks 
> {code}
> Index: src/hdfs/org/apache/hadoop/hdfs/server/namenode/PermissionChecker.java
> ===================================================================
> --- src/hdfs/org/apache/hadoop/hdfs/server/namenode/PermissionChecker.java	(revision
768189)
> +++ src/hdfs/org/apache/hadoop/hdfs/server/namenode/PermissionChecker.java	(working copy)
> @@ -40,6 +40,7 @@
>      if (LOG.isDebugEnabled()) {
>        LOG.debug("ugi=" + ugi);
>      }
> +    LOG.info("ugi=" + ugi);
>  
>      if (ugi != null) {
>        user = ugi.getUserName();
> {code}
> While initializing a job, the ugi information should point to jobtracker as jobtracker
does a dfs read. But today we will see that the log shows _pi_ as the caller instead of the
jobtracker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message