[
https://issues.apache.org/jira/browse/YARN-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931320#comment-13931320
]
Hadoop QA commented on YARN-1812:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12634082/YARN-1812.2.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 7 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}. There were no new javadoc 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3328//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3328//console
This message is automatically generated.
> Job stays in PREP state for log time after RM Restarts
> ------------------------------------------------------
>
> Key: YARN-1812
> URL: https://issues.apache.org/jira/browse/YARN-1812
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Yesha Vora
> Assignee: Jian He
> Attachments: YARN-1812.1.patch, YARN-1812.2.patch
>
>
> Steps followed:
> 1) start a sort job with 80 maps and 5 reducers
> 2) restart Resource manager when 60 maps and 0 reducers are finished
> 3) Wait for job to come out of PREP state.
> The job does not come out of PREP state after 7-8 mins.
> After waiting for 7-8 mins, test kills the job.
> However, Sort job should not take this long time to come out of PREP state
--
This message was sent by Atlassian JIRA
(v6.2#6252)
