You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/04/20 01:41:15 UTC

[jira] [Created] (TEZ-52) Fix YARNRunner to have jobStatus so that it does not throw exception after job success

Bikas Saha created TEZ-52:
-----------------------------

             Summary: Fix YARNRunner to have jobStatus so that it does not throw exception after job success
                 Key: TEZ-52
                 URL: https://issues.apache.org/jira/browse/TEZ-52
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Bikas Saha
            Assignee: Hitesh Shah


13/04/17 16:19:44 INFO mapreduce.ClientServiceDelegate: Application state is completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server
13/04/17 16:19:45 INFO mapreduce.JobSubmitter: Cleaning up the staging area /tmp/hadoop-yarn/staging/bikas/.staging/job_1366230194620_0007
13/04/17 16:19:45 ERROR security.UserGroupInformation: PriviledgedActionException as:bikas (auth:SIMPLE) cause:java.io.IOException: Could not launch job
java.io.IOException: Could not launch job
        at org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:417)
        at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1218)
        at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1215)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1489)
        at org.apache.hadoop.mapreduce.Job.submit(Job.java:1215)
        at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1236)
        at org.apache.hadoop.examples.WordCount.main(WordCount.java:84)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Na

--
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