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

Siqi Li commented on YARN-1714:
-------------------------------

For question 1, yes we do have full text search over the app list. By doing 
this, we can filter the apps on the server side. So, user will not be bothered 
by other people's jobs. Also, once we need to add security, it's better to see 
the apps that you own. 
2. I'm not aware of any REST API does the same thing, can you give me some 
examples?
3. For now, users have to edit url, but we can also provide direct link where 
people can click to get in this page. Moreover, we can automatically take user 
name and call this new url directly in the future when turning on security.
4. yes, we should reuse AppsBlock.

> Per user and per queue view in YARN RM
> --------------------------------------
>
>                 Key: YARN-1714
>                 URL: https://issues.apache.org/jira/browse/YARN-1714
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>            Priority: Critical
>         Attachments: YARN-1714.v1.patch, YARN-1714.v2.patch, 
> YARN-1714.v3.patch
>
>
> ResourceManager exposes either one or all jobs via WebUI. It would be good to 
> have filter for user so that see only their jobs.
> Provide rest style url to access only user specified queue or user apps. 
> For instance,
> http://hadoop-example.com:50030/cluster/user/toto                             
>             displays apps owned by toto
> http://hadoop-example.com:50030/cluster/user/toto,glinda                      
>         displays apps owned by toto and glinda
> http://hadoop-example.com:50030/cluster/queue/root.queue1                     
>    displays apps in root.queue1
> http://hadoop-example.com:50030/cluster/queue/root.queue1,root.queue2   
> displays apps in root.queue1 and  root.queue2



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to