[
https://issues.apache.org/jira/browse/MAPREDUCE-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181662#comment-13181662
]
Hadoop QA commented on MAPREDUCE-3382:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12509721/MAPREDUCE-3382.branch-0.23.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 1 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 .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1558//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1558//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1558//console
This message is automatically generated.
> Network ACLs can prevent AMs to ping the Job-end notification URL
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-3382
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3382
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, mrv2
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Ravi Prakash
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3382.branch-0.23.patch
>
>
> MAPREDUCE-3028 added support for job-end notification from MR AMs after the
> job finishes. Network ACLs can have an implication on this one - outgoing
> connections from the compute nodes may be restricted in some settings and so
> job-end notification( that can originate from the AMs which may run on random
> nodes in the cluster) may have issues.
--
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
