[
https://issues.apache.org/jira/browse/YARN-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840932#comment-13840932
]
Karthik Kambatla commented on YARN-1139:
----------------------------------------
I was under the impression that the long-term goal was to use services where
applicable.
My primary rationale for this JIRA was to reduce the time to transition to
Active in the long-term, or to support a "warmer" Standby mode. Converting all
the components to services is not absolutely required for that. It might be
nice to make the scheduler a service, so individual schedulers can take up the
task of handling start/stop etc. There could be a single SecretManagerService
that handles the lifecycle of all YARN-related *SecretManagers. [~vinodkv],
does that sound like a more reasonable approach?
> [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)
