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

Naganarasimha G R commented on YARN-3880:
-----------------------------------------

Hi [~sjlee0], [~gtCarrera] & [~djp],
Regarding this jira i had few queries, 
# *runningContainers* it makes more sense to capture only when we periodically 
collect this stats when app is in running state. Is that the intention ?  
*memorySeconds & vcoreSeconds* is already being captured in V1 as well as V2 
when application is finished.  Are these planned to be captured periodically? I 
feel current Container Metrics which are getting aggregated  also gives some 
thing in the same lines also if captured in RM periodically for all apps, then 
load on the RM will be more. But if required, similar to the ContainerMonitor i 
can create AppMonitor and collect these stats and publish them to ATSV2 
# preemptedResourceMB and other info related to preemption are not captured, 
but again like previous query do we need to capture periodically or is it 
sufficient to capture it at the end of the app?


> Writing more RM side app-level metrics
> --------------------------------------
>
>                 Key: YARN-3880
>                 URL: https://issues.apache.org/jira/browse/YARN-3880
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Naganarasimha G R
>
> In YARN-3044, we implemented an analog of metrics publisher for ATS v1. While 
> it helps to write app/attempt/container life cycle events, it really doesn't 
> write  as many app-level system metrics that RM are now having.  Just list 
> the metrics that I found missing:
> * runningContainers
> * memorySeconds
> * vcoreSeconds
> * preemptedResourceMB
> * preemptedResourceVCores
> * numNonAMContainerPreempted
> * numAMContainerPreempted
> Please feel fee to add more into the list if you find it's not covered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to