[
https://issues.apache.org/jira/browse/MAPREDUCE-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101253#comment-13101253
]
Hudson commented on MAPREDUCE-2937:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #812 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/812/])
MAPREDUCE-2937. Ensure reason for application failure is displayed to the
user. Contributed by Mahadev Konar.
acmurthy :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166966
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/java/org/apache/hadoop/mapred/YARNRunner.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/TestYARNRunner.java
> Errors in Application failures are not shown in the client trace.
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-2937
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2937
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Critical
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2937.patch, MAPREDUCE-2937.patch,
> MAPREDUCE-2937.patch
>
>
> The client side does not show enough information on why the job failed. Here
> is step to reproduce it:
> 1) set the scheduler to be capacity scheduler with queues a, b
> 2) submit a job to a queue that is not a,b
> The job just fails without saying why it failed. We should have enough trace
> log at the client side to let the user know why it failed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
