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

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

bq. Is the way we are planning this patch?
Yes [~sunilg], as per the latest discussion we thought this would be better 
than going to the approach similar to Queue user metrics, which the attached 
WIP patch tries to solve.

Earlier i thought it would be easy to discuss if atleast one WIP patch to 
understand the final metrics structure. But yes you are right we can just take 
the output of the existing command and update how we want the final structure 
of the output.
[~maniraj...@gmail.com], can you please try take the existing scheduler metrics 
 output and share the structure which we want to propose ?


> Generate queue metrics for each partition
> -----------------------------------------
>
>                 Key: YARN-6492
>                 URL: https://issues.apache.org/jira/browse/YARN-6492
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacity scheduler
>            Reporter: Jonathan Hung
>            Assignee: Manikandan R
>         Attachments: YARN-6492.001.patch
>
>
> We are interested in having queue metrics for all partitions. Right now each 
> queue has one QueueMetrics object which captures metrics either in default 
> partition or across all partitions. (After YARN-6467 it will be in default 
> partition)
> But having the partition metrics would be very useful.



--
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