Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-5395

When queue ACLs are enabled, the error message shown when a job is submitted to a non-existent queue is misleading

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.20.0
    • None
    • None
    • Reviewed

    Description

      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.

      Attachments

        1. exceptionpath
          2 kB
          rahul k singh
        2. HADOOP-5395.patch
          2 kB
          rahul k singh

        Activity

          People

            rksingh rahul k singh
            yhemanth Hemanth Yamijala
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: