hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4448) Nodemanager crashes upon application cleanup if aggregation failed to start
Date Tue, 17 Jul 2012 13:35:34 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416173#comment-13416173
] 

Daryn Sharp commented on MAPREDUCE-4448:
----------------------------------------

I wonder if {{stopContainer}} should even be called with initialization fails?  It's only
purpose is to start aggregating but the aggregator isn't present if initialization fails.
 Maybe the event handler should only invoke {{stopContainer}} if initialization is successful?

Otherwise I question if the log message is necessary, or if it should at least be downgraded
(debug or info?) since it really isn't a problem.
                
> Nodemanager crashes upon application cleanup if aggregation failed to start
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4448
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4448
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, nodemanager
>    Affects Versions: 0.23.3, 2.0.1-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: MAPREDUCE-4448.patch
>
>
> When log aggregation is enabled, the nodemanager can crash if log aggregation for an
application failed to start.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message