[
https://issues.apache.org/jira/browse/YARN-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766597#comment-13766597
]
Hadoop QA commented on YARN-1183:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12603037/YARN-1183--n3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1916//console
This message is automatically generated.
> MiniYARNCluster shutdown takes several minutes intermittently
> -------------------------------------------------------------
>
> Key: YARN-1183
> URL: https://issues.apache.org/jira/browse/YARN-1183
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Andrey Klochkov
> Attachments: YARN-1183--n2.patch, YARN-1183--n3.patch, YARN-1183.patch
>
>
> As described in MAPREDUCE-5501 sometimes M/R tests leave MRAppMaster java
> processes living for several minutes after successful completion of the
> corresponding test. There is a concurrency issue in MiniYARNCluster shutdown
> logic which leads to this. Sometimes RM stops before an app master sends it's
> last report, and then the app master keeps retrying for >6 minutes. In some
> cases it leads to failures in subsequent tests, and it affects performance of
> tests as app masters eat resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
