[HADOOP-5737] UGI checks in testcases are broken

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Component/s: security, test
• Hadoop Flags: Reviewed
• Release Note: Fixed JobTracker to use it's own credentials instead of the job's credentials for accessing mapred.system.dir. Also added APIs in the JobTracker to get the FileSystem objects as per the JobTracker's configuration.
• Assignee: Amar Kamat
• Reporter: Amar Kamat
• Created: 24/Apr/09 07:21
• Updated: 24/Aug/10 20:37
• Resolved: 12/May/09 09:04

Description

While running TestMiniMRWithDFSWithDistinctUsers, I used this patch to test the ugi checks

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();

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.

Issue Links

• blocks: MAPREDUCE-181 Secure job submission