[
https://issues.apache.org/jira/browse/MAPREDUCE-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287546#comment-13287546
]
Hadoop QA commented on MAPREDUCE-4302:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12530572/MAPREDUCE-4302.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2430//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2430//console
This message is automatically generated.
> NM goes down if error encountered during log aggregation
> --------------------------------------------------------
>
> Key: MAPREDUCE-4302
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4302
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 0.23.0, 2.0.0-alpha, trunk
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: MAPREDUCE-4302.patch
>
>
> When a container launch request is sent to the NM, if _any_ exception occurs
> during the init of log aggregation then the NM goes down. The problem can be
> induced by situations including, but certainly not limited to: transient rpc
> connection issues, missing tokens, expired tokens, permissions, full/quota
> exceeded dfs, etc. The problem may occur with and without security enabled.
> The ramification is an entire cluster can be rather easily brought down
> either maliciously, accidentally, or via a submission bug.
--
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
