[
https://issues.apache.org/jira/browse/MAPREDUCE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved MAPREDUCE-5714.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.4.1
trunk
Release Note: Thanks Jinghui
> TestMRAppComponentDependencies causes surefire to exit without saying proper
> goodbye
> ------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5714
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5714
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Affects Versions: 2.2.0
> Environment: RHEL 6.4
> Reporter: Jinghui Wang
> Assignee: Jinghui Wang
> Fix For: trunk, 2.4.1
>
> Attachments: MAPREDUCE-5714.patch
>
>
> When running test TestMRAppComponentDependencies, surefire exits with the
> following message:
> Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
> project hadoop-mapreduce-client-app: ExecutionException; nested exception is
> java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
> forked VM terminated without saying properly goodbye. VM crash or System.exit
> called ?
> The following code is found in
> o.a.h.mapreduce.v2.app.MRAppMaster#shutDownJob, which the test case inherits.
> So, before the test testComponentStopOrder completes in
> TestMRAppComponentDependencies, shutDownJob finishes executing and exits the
> JVM, thus causing the error. Based on the comment, the System.exit(0) is
> there as a workaround for before HADOOP-7140. Since the patch for HADOOP-7140
> is committed in branch-2, are we safe to remove the System.exit call now.
> //Bring the process down by force.
> //Not needed after HADOOP-7140
> LOG.info("Exiting MR AppMaster..GoodBye!");
> sysexit();
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
