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

Zhijie Shen commented on YARN-1001:
-----------------------------------

Vinod, thanks for committing the patch. In addition to the new feature we added 
in this jira, some additional thought came into my mind:

1. RMContext store all the applications in one map. This data structure is not 
friendly to GetApps and GetAppStatistics, which need to go through the whole 
collection. Given some regular query criteria, such as states and 
applicationTypes, it would be good if we can somehow index the apps according 
to these criteria. Therefore, we can speed up the two APIs, maybe also some 
other operations on the app collection of RMContext. 

2. Now web API ignores the case when matching the applicationType. IMHO, 
ApplicationClientProtocol should have the same behavior. Moreover, I think it's 
good to define criteria of naming an applicationType, for example, letter and  
number only, case insensitive and etc.

Thoughts?
                
> YARN should provide per application-type and state statistics
> -------------------------------------------------------------
>
>                 Key: YARN-1001
>                 URL: https://issues.apache.org/jira/browse/YARN-1001
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: api
>    Affects Versions: 2.1.0-beta
>            Reporter: Srimanth Gunturi
>            Assignee: Zhijie Shen
>            Priority: Blocker
>             Fix For: 2.1.1-beta
>
>         Attachments: YARN-1001.1.patch, YARN-1001.2.patch, YARN-1001.3.patch, 
> YARN-1001.4.patch, YARN-1001.5.patch, YARN-1001.6.patch, YARN-1001.7.patch
>
>
> In Ambari we plan to show for MR2 the number of applications finished, 
> running, waiting, etc. It would be efficient if YARN could provide per 
> application-type and state aggregated counts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to