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

Jian He commented on YARN-7215:
-------------------------------

I didn't mean to make RM store the app configs.... in fact, RM has even no way 
to get the app configs, yarn-service is just an app to RM's point of view. RM 
can only store the metaData of YARN.

Isn't this jira, by description,  to implement "slider list" ? that is as 
simple as get the list of apps with some meta status info, which "yarn 
application -list" command already does today.  I don't  think we need a solr 
backend to support such simple use-case. That is also how "slider list" worked 
before... User should be able to simply list services without solr in the 
picture, just similar to listing apps.

I guess you meant bigger things in YARN-7129 to index apps by configs with solr 
or something? 
If this jira is meant to implement bigger things in YARN-7129,  I can probably 
open a separate jira to implement "yarn service list" command, which is a 
fairly simple patch


> REST API to list all deployed services by the same user
> -------------------------------------------------------
>
>                 Key: YARN-7215
>                 URL: https://issues.apache.org/jira/browse/YARN-7215
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, applications
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>
> In Slider, it is possible to list deployed applications from the same user by 
> using:
> {code}
> slider list
> {code}
> This API can help UI to display application and services deployed by the same 
> user.
> Apiserver does not have ability to list all applications/services at this 
> time.  This API requires fast response to list all applications because it is 
> a common UI operation.  ApiServer deployed applications persist configuration 
> in HDFS similar to slider, but using directory listing to display deployed 
> application might cost too much overhead to namenode.  We may want to use 
> alternative storage mechanism to cache deployed application configuration to 
> accelerate the response time of list deployed applications.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to