[
https://issues.apache.org/jira/browse/MAPREDUCE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146621#comment-13146621
]
Hadoop QA commented on MAPREDUCE-3312:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12502972/MR-3312.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 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 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 .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1274//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1274//console
This message is automatically generated.
> Make MR AM not send a stopContainer w/o corresponding start container
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-3312
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3312
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Fix For: 0.23.1
>
> Attachments: MR-3312.txt
>
>
> This is a follow on to MAPREDUCE-3274. It is possible, although rare, for
> the MR AM to send a stop container before it sends a start container. This
> needs to stop that from happening. If a stop is found first it should
> prevent the start from being sent. It tries to do this, but only if the stop
> is currently pending.
--
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
