[
https://issues.apache.org/jira/browse/YARN-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414982#comment-16414982
]
Wangda Tan commented on YARN-8048:
----------------------------------
Thanks [~rohithsharma],
For
{quote}Right, for non RM deployment scenarios to handle I added this. Though
non RM deployment not used, I think its better to keep it.
{quote}
I would prefer to not do it for now, let's focus on the must-to-have
requirements in this Jira.
{quote}I will check the feasibility and let me update the patch based on this.
{quote}
Thanks, I'm also fine if this part can be easier replaced, for this use case,
it's better to use Client-like API instead of using REST API.
> Support auto-spawning of admin configured services during bootstrap of
> rm/apiserver
> -----------------------------------------------------------------------------------
>
> Key: YARN-8048
> URL: https://issues.apache.org/jira/browse/YARN-8048
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Major
> Attachments: YARN-8048.001.patch, YARN-8048.002.patch
>
>
> Goal is to support auto-spawning of admin configured services during
> bootstrap of resourcemanager/apiserver.
> *Requirement:* Some of the services might required to be consumed by yarn
> itself ex: Hbase for atsv2. Instead of depending on user installed HBase or
> sometimes user may not required to install HBase at all, in such conditions
> running HBase app on YARN will help for ATSv2.
> Before YARN cluster is started, admin configure these services spec and place
> it in common location in HDFS. At the time of RM/apiServer bootstrap, these
> services will be submitted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
