You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2013/10/16 21:21:43 UTC

[jira] [Commented] (YARN-1139) [Umbrella] Convert all RM components to Services

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

Zhijie Shen commented on YARN-1139:
-----------------------------------

When converting the components into services, one thing I think we may need to take care is that the exception will be isolated by the service model. For example,
{code}
    try {
      this.scheduler.reinitialize(conf, this.rmContext);
    } catch (IOException ioe) {
      throw new RuntimeException("Failed to initialize scheduler", ioe);
    }
{code}
If the scheduler turns into a service, RM cannot catch the exception like that.

Previously, we also met the problem of the composite service cannot directly receive the exception that is thrown by its child.

> [Umbrella] Convert all RM components to Services
> ------------------------------------------------
>
>                 Key: YARN-1139
>                 URL: https://issues.apache.org/jira/browse/YARN-1139
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>            Assignee: Tsuyoshi OZAWA
>
> Some of the RM components - state store, scheduler etc. are not services. Converting them to services goes well with the "Always On" and "Active" service separation proposed on YARN-1098.
> Given that some of them already have start(), stop() methods, it should not be too hard to convert them to services.
> That would also be a cleaner way of addressing YARN-1125.



--
This message was sent by Atlassian JIRA
(v6.1#6144)