You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/10/14 16:05:44 UTC

[jira] [Resolved] (MAPREDUCE-5581) killing jobs which have failed causes log missing

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

Jason Lowe resolved MAPREDUCE-5581.
-----------------------------------

    Resolution: Duplicate

This is a duplicate of MAPREDUCE-5502.

> killing jobs which have failed causes log missing
> -------------------------------------------------
>
>                 Key: MAPREDUCE-5581
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5581
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.1.1-beta
>            Reporter: Nemon Lou
>
> In hive code,when a job failed,they invoke the RunningJob.killJob() API immediately.
> From mapreduce client side,when job is at failed state,the YARNRunner will invoke resMgrDelegate.killApplication to kill that job.And this prevent AM from writing logs to job history server.



--
This message was sent by Atlassian JIRA
(v6.1#6144)