[
https://issues.apache.org/jira/browse/HADOOP-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681284#action_12681284
]
Hemanth Yamijala commented on HADOOP-5395:
------------------------------------------
Code changes look good. +1.
> When queue ACLs are enabled, the error message shown when a job is submitted
> to a non-existent queue is misleading
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5395
> URL: https://issues.apache.org/jira/browse/HADOOP-5395
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Hemanth Yamijala
> Assignee: rahul k singh
> Fix For: 0.21.0
>
> Attachments: exceptionpath, HADOOP-5395.patch
>
>
> When acls are enabled on the job tracker using the property
> mapred.acls.enabled, and a job is submitted to a queue name that does not
> exist in mapred.queue.names property, the following exception is thrown:
> org.apache.hadoop.security.AccessControlException:
> org.apache.hadoop.security.AccessControlException: User user-name cannot
> perform operation SUBMIT_JOB on queue queue-name
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:96)
> at
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:58)
>
> The message makes it appear like the queue exists, but the user does not have
> access to it, where the actual problem is that the queue does not exist at
> all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
