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 Fri, 25 Oct 2013 19:02:39 GMT

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

Karthik Kambatla commented on YARN-1318:
----------------------------------------

To move forward on this, I propose RMContext should be more along the lines of a Builder -
default constructor (no arguments) and use set* methods to set the internal fields. [~vinodkv],
does this sound reasonable? If yes, it might make sense to open a new JIRA for that? 

> 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: Critical
>              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
(v6.1#6144)

Mime
View raw message