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

Posted to mapreduce-issues@hadoop.apache.org by "Gera Shegalov (JIRA)" <ji...@apache.org> on 2016/03/21 19:05:25 UTC

[jira] [Updated] (MAPREDUCE-6315) Implement retrieval of logs for crashed MR-AM via jhist in the staging directory

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

Gera Shegalov updated MAPREDUCE-6315:
-------------------------------------
    Attachment: MAPREDUCE-6315.002.patch

Ran into an AM crash again, and found this AM log recovery really useful. So rebasing and fixing the test failures (flush count because I am making AM_STARTED forcelogged).  

> Implement retrieval of logs for crashed MR-AM via jhist in the staging directory
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6315
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6315
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client, mr-am
>    Affects Versions: 2.7.0
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>            Priority: Critical
>              Labels: BB2015-05-TBR
>         Attachments: MAPREDUCE-6315.001.patch, MAPREDUCE-6315.002.patch
>
>
> When all AM attempts crash, there is no record of them in JHS. Thus no easy way to get the logs. This JIRA automates the procedure by utilizing the jhist file in the staging directory. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)