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 "Mohammad Kamrul Islam (JIRA)" <ji...@apache.org> on 2014/01/14 23:51:19 UTC

[jira] [Updated] (MAPREDUCE-5723) MR AM container log empty if exception occurs

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

Mohammad Kamrul Islam updated MAPREDUCE-5723:
---------------------------------------------

    Attachment: MAPREDUCE-5723.1.patch

patch uploaded.

> MR AM container log empty if exception occurs
> ---------------------------------------------
>
>                 Key: MAPREDUCE-5723
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5723
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster
>    Affects Versions: 2.2.0
>            Reporter: Mohammad Kamrul Islam
>            Assignee: Mohammad Kamrul Islam
>             Fix For: trunk, 2.2.0
>
>         Attachments: MAPREDUCE-5723.1.patch
>
>
> It occurs when the property "mapreduce.task.userlog.limit.kb" is set non-zero in mapped-site.xml.
> AM container syslog remains empty if any exception occurs. 
> Bug details:
> In MRAppMaster.java, the following code snippets show the bug.
> } catch (Throwable t) {
>        LOG.fatal("Error starting MRAppMaster", t);
>       System.exit(1);
>     }finally {
>        LogManager.shutdown();
>      }
> In the catch block, we are exiting the JVM. So finally block (therefore LogManager.shutdown()) is never executed.
> Possible fix: 
> Make sure LogManager.shutdown() is executed in all cases.
>  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)