[
https://issues.apache.org/jira/browse/YARN-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416804#comment-16416804
]
Rohith Sharma K S commented on YARN-8048:
-----------------------------------------
bq. I think we should hardcode this one unless we have any use case requires
pluggability.
Agree
bq. I think we should skip system services if the folder doesn't exist.
Agree. Admin need to create explicitly and give as yarn daemon user permission.
bq. Why 777 permission?
Ahh.. It should be 700 permission. Only yarn user can access it. Given yarn
service expect a system service folder to be present, we need not to apply
permission. This can be removed.
bq. it's better to only read files ended with .yarnfile.
Agree
bq. It's better to make user name(s) configurable in yarn-site.xml .
Services should be able to launch for any users. Same service can be launched
by different user. Configuration will bring up additional work to admin after
adding a yarn-file under system directory. User->Services mapping would grow
more. Going with user folder makes easier for adding service for admin create
folder and keep yarn files under user folder.
bq. Otherwise some user could put some random folders which is recognized as
user name and cause failure/security issues.
As part of security, only admin specifically yarn user have permission to
access this folder. This folder should be precreate with right permissions. No
arbitrary users can create a folder under system-service directory. From code
perspective, any empty folder under system-service are ignored.
bq. I'm not sure if we should make system service launch asynchronized or
synchronized. To me it makes more sense to launch synchronized.
making synchronization will delay RM transition period if more services to be
started.
bq. Renames:
Agree
> 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,
> YARN-8048.003.patch, YARN-8048.004.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
