hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5723) MR AM container log truncated on normal execution or empty if exception occurs
Date Wed, 22 Jan 2014 14:44:23 GMT

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

Jason Lowe updated MAPREDUCE-5723:
----------------------------------

            Priority: Critical  (was: Major)
    Target Version/s: 2.4.0
       Fix Version/s:     (was: 2.2.0)
                          (was: trunk)
             Summary: MR AM container log truncated on normal execution or empty if exception
occurs  (was: MR AM container log empty if exception occurs)

Elevating priority and updating the summary since this is subsuming MAPREDUCE-5730, and AM
logs are essentially broken since MAPREDUCE-5694.

Also the Fix Version/s field in JIRA should only be filled out when the patch is committed
to indicate where it has been fixed.  The Target Version/s field indicates where the JIRA
is targeted to be fixed.

> MR AM container log truncated on normal execution or 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
>            Priority: Critical
>         Attachments: MAPREDUCE-5723.1.patch, MAPREDUCE-5723.2.patch, MAPREDUCE-5723.3.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.
> {code}
>     } catch (Throwable t) {
>        LOG.fatal("Error starting MRAppMaster", t);
>       System.exit(1);
>     }finally {
>        LogManager.shutdown();
>     }
> {code}
> 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)

Mime
View raw message