hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2937) Errors in Application failures are not shown in the client trace.
Date Thu, 08 Sep 2011 21:45:09 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mahadev konar updated MAPREDUCE-2937:
-------------------------------------

    Status: Patch Available  (was: Open)

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

        

Mime
View raw message