[
https://issues.apache.org/jira/browse/HADOOP-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat resolved HADOOP-5541.
--------------------------------
Resolution: Duplicate
Duplicate of HADOOP-3906. Plz comment there.
> Place holder for job level diagnostic information
> -------------------------------------------------
>
> Key: HADOOP-5541
> URL: https://issues.apache.org/jira/browse/HADOOP-5541
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Vinod K V
>
> In some scenarios, when framework itself fails/kills the job, there is no
> clear way for the user to know what happened to the job. A job level
> diagnostic string, perhaps displayed in JobStatus when queried from command
> line or view from the web ui would help. Two cases I can think of:
> - When a job is failed when it transgresses
> mapred.jobtracker.maxtasks.per.job.
> - When CapacityScheduler kills a job when it detects that the job's memory
> requirements can never be meant.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
