[ https://issues.apache.org/jira/browse/YARN-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765891#comment-13765891
]
Hadoop QA commented on YARN-1183:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12602875/YARN-1183--n2.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:green}+1 javac{color}. The applied patch does not increase the total number of
javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version
1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase the total number
of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-YARN-Build/1905//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1905//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.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
|