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

Rohith Sharma K S commented on YARN-8048:
-----------------------------------------

bq. For the 2nd level, it's better to only read files ended with .yarnfile
I am in dilemma! Given native service framework is enforcing all spec file to 
be ended with .yarnfile i.e making standardized spec file extension, it make 
sense to check file extension. Otherwise it is normal json file which NOT 
required to check for file extension. However in my last patch I incorporated 
this file extension check, but I am _not sure_ does native service going to 
make it standard. I see that from CLI command which submits a service reads 
normal json file i.e ApiServiceClient#loadAppJsonFromLocalFS. It doesn't check 
for yarnfile extension. 

bq. I'm not sure about correctness of this behavior.
Though it is called as async mode, it doesn't executed after some delay. It is 
started in separate thread which in turn launches services in no time. This 
makes admin service to release lock faster during transitioning to active 
phase. However, going with sync and async folder hierarchy also make sense to 
me. I will update the patch with this change.

> 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, YARN-8048.005.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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to