hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1318) Promote AdminService to an Always-On service
Date Mon, 28 Oct 2013 17:20:31 GMT

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

Karthik Kambatla commented on YARN-1318:

Thanks for chipping in, Vinod. 

bq. The current method of passing in whatever is possible in constructor and set the remaining
using setters when they are ready should continue to work. Why do we need to change it?
If AdminService moves to Always-On service, even the RMContext needs to be created before
AdminService. None of the ActiveServices are created yet by that point, and hence the need
for that change.

> Promote AdminService to an Always-On service
> --------------------------------------------
>                 Key: YARN-1318
>                 URL: https://issues.apache.org/jira/browse/YARN-1318
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.3.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Blocker
>              Labels: ha
> Per discussion in YARN-1068, we want AdminService to handle HA-admin operations in addition
to the regular non-HA admin operations. To facilitate this, we need to move AdminService an
Always-On service. 

This message was sent by Atlassian JIRA

View raw message