[jira] [Commented] (YARN-288) Fair scheduler queue doesn't accept any jobs when ACLs are configured.

2013-01-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543853#comment-13543853
 ] 

Hudson commented on YARN-288:
-

Integrated in Hadoop-Hdfs-trunk #1275 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1275/])
YARN-288. Fair scheduler queue doesn't accept any jobs when ACLs are 
configured. Contributed by Sandy Ryza. (Revision 1428362)

 Result = FAILURE
tomwhite : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1428362
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSParentQueue.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSQueue.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/QueueManager.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java


 Fair scheduler queue doesn't accept any jobs when ACLs are configured.
 --

 Key: YARN-288
 URL: https://issues.apache.org/jira/browse/YARN-288
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager, scheduler
Affects Versions: 2.0.2-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.3-alpha

 Attachments: YARN-288.patch


 If a queue is configured with an ACL for who can submit jobs, no jobs are 
 allowed, even if a user on the list tries.
 This is caused by using the scheduler thinking the user is yarn, because it 
 calls UserGroupInformation.getCurrentUser() instead of 
 UserGroupInformation.createRemoteUser() with the given user name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-288) Fair scheduler queue doesn't accept any jobs when ACLs are configured.

2013-01-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543897#comment-13543897
 ] 

Hudson commented on YARN-288:
-

Integrated in Hadoop-Mapreduce-trunk #1305 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1305/])
YARN-288. Fair scheduler queue doesn't accept any jobs when ACLs are 
configured. Contributed by Sandy Ryza. (Revision 1428362)

 Result = SUCCESS
tomwhite : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1428362
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSParentQueue.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSQueue.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/QueueManager.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java


 Fair scheduler queue doesn't accept any jobs when ACLs are configured.
 --

 Key: YARN-288
 URL: https://issues.apache.org/jira/browse/YARN-288
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager, scheduler
Affects Versions: 2.0.2-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.3-alpha

 Attachments: YARN-288.patch


 If a queue is configured with an ACL for who can submit jobs, no jobs are 
 allowed, even if a user on the list tries.
 This is caused by using the scheduler thinking the user is yarn, because it 
 calls UserGroupInformation.getCurrentUser() instead of 
 UserGroupInformation.createRemoteUser() with the given user name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-288) Fair scheduler queue doesn't accept any jobs when ACLs are configured.

2013-01-02 Thread Sandy Ryza (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542422#comment-13542422
 ] 

Sandy Ryza commented on YARN-288:
-

Test failure is unrelated.

 Fair scheduler queue doesn't accept any jobs when ACLs are configured.
 --

 Key: YARN-288
 URL: https://issues.apache.org/jira/browse/YARN-288
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager, scheduler
Affects Versions: 2.0.2-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.3-alpha

 Attachments: YARN-288.patch


 If a queue is configured with an ACL for who can submit jobs, no jobs are 
 allowed, even if a user on the list tries.
 This is caused by using the scheduler thinking the user is yarn, because it 
 calls UserGroupInformation.getCurrentUser() instead of 
 UserGroupInformation.createRemoteUser() with the given user name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira