hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5541) Place holder for job level diagnostic information
Date Fri, 20 Mar 2009 10:32:51 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683833#action_12683833
] 

Vinod K V commented on HADOOP-5541:
-----------------------------------

bq.  - When CapacityScheduler kills a job when it detects that the job's memory requirements
can never be meant.
When CapacityScheduler kills a job when it detects that the job's memory requirements can
never be *met*.

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


Mime
View raw message