hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1165) Move init() of activeServices to ResourceManager#serviceStart()
Date Tue, 10 Sep 2013 01:31:53 GMT

    [ https://issues.apache.org/jira/browse/YARN-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762589#comment-13762589

Bikas Saha commented on YARN-1165:

I had considered this option but did not propose it because of the stop() calling create and
init. It sounds weird. If you also think that this approach sounds fine then lets do it. On
a +ve not, it also means that active services are ready to go as soon as the signal comes

> Move init() of activeServices to ResourceManager#serviceStart()
> ---------------------------------------------------------------
>                 Key: YARN-1165
>                 URL: https://issues.apache.org/jira/browse/YARN-1165
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: test-failures.pdf
> Background: 
> # YARN-1098 separates out RM services into Always-On and Active services, but doesn't
change the behavior in any way.
> # For YARN-1027, we would want to create, initialize, and start RMActiveServices in the
scope of RM#serviceStart(). This requires updating test cases that check for certain behavior
post RM#serviceInit() - otherwise, most of these tests NPE.
> Creating a JIRA different from YARN-1027 to address all these test cases.

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

View raw message