[
https://issues.apache.org/jira/browse/YARN-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742644#comment-13742644
]
Hadoop QA commented on YARN-1075:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12598537/yarn-1075-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1734//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1734//console
This message is automatically generated.
> AsyncDispatcher and ResourceTrackerService violate serviceStart() semantics
> ---------------------------------------------------------------------------
>
> Key: YARN-1075
> URL: https://issues.apache.org/jira/browse/YARN-1075
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Priority: Minor
> Attachments: yarn-1075-1.patch
>
>
> IIUC, the serviceStart() implementation of services should start local
> threads/services first before calling super.serviceStart(). Certain services
> have this reversed as below - leading to possibilities where the service
> would be in state STARTED, but in reality might not have started yet.
> {code}
> void serviceStart() {
> super.serviceStart()
> // service sepecific logic and start operations
> }
> {code}
--
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
