[jira] [Commented] (MAPREDUCE-6020) Too many threads blocking on the global JobTracker lock from getJobCounters, optimize getJobCounters to release global JobTracker lock before access the per job cou

2015-05-08 Thread Ameya Sakhalkar (JIRA) 

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14533948#comment-14533948
 ] 

Ameya Sakhalkar commented on MAPREDUCE-6020:


Looks good to me.

 Too many threads blocking on the global JobTracker lock from getJobCounters, 
 optimize getJobCounters to release global JobTracker lock before access the 
 per job counter in JobInProgress
 -

 Key: MAPREDUCE-6020
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6020
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
Affects Versions: 0.23.10
Reporter: zhihai xu
Assignee: zhihai xu
  Labels: BB2015-05-TBR
 Attachments: MAPREDUCE-6020.branch1.patch


 Too many threads blocking on the global JobTracker lock from getJobCounters, 
 optimize getJobCounters to release global JobTracker lock before access the 
 per job counter in JobInProgress. It may be a lot of JobClients to call 
 getJobCounters in JobTracker at the same time, Current code will lock the 
 JobTracker to block all the threads to get counter from JobInProgress. It is 
 better to unlock the JobTracker when get counter from 
 JobInProgress(job.getCounters(counters)). So all the theads can run parallel 
 when access its own job counter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MAPREDUCE-4070) JobHistoryServer creates /tmp directory with restrictive permissions if the directory doesn't already exist.

2015-05-08 Thread Ameya Sakhalkar (JIRA) 

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14534166#comment-14534166
 ] 

Ameya Sakhalkar commented on MAPREDUCE-4070:


Tried to reproduce with version 2.5.0. Deleted /tmp and restarted 
HistoryServer. It created /tmp with permissions 770:
drwxrwx---   - hadoop supergroup  0 2015-05-08 14:17 /tmp


 JobHistoryServer creates /tmp directory with restrictive permissions if the 
 directory doesn't already exist.
 

 Key: MAPREDUCE-4070
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4070
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: mrv2
Affects Versions: 0.23.1
Reporter: Ahmed Radwan
Assignee: Ahmed Radwan
  Labels: BB2015-05-TBR
 Attachments: MAPREDUCE-4070.patch


 Starting up the MapReduce JobhHistoryServer service after a clean install 
 appears to automatically create the /tmp directory on HDFS. However, it is 
 created with 750 permission.
 Attempting to run MR jobs by other users results in the following permissions 
 exception:
 {code}
 org.apache.hadoop.security.AccessControlException: Permission denied: 
 user=cloudera, access=EXECUTE, inode=/tmp:yarn:supergroup:drwxr-x---
 at 
 org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:205)
 ..
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)