[ https://issues.apache.org/jira/browse/YARN-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490570#comment-16490570 ]
Weiwei Yang commented on YARN-8213: ----------------------------------- Hi [~leftnoteasy] Makes sense to me. I just uploaded a new patch, added {{ResourceScheduler#resetSchedulerMetrics}}, once other scheduler has their own metrics implementation, they just need to override this method. It's hard to abstract out a scheduler metrics base class because different schedulers are recording different counters. Please let me know if this makes sense, thanks. > Add Capacity Scheduler metrics > ------------------------------ > > Key: YARN-8213 > URL: https://issues.apache.org/jira/browse/YARN-8213 > Project: Hadoop YARN > Issue Type: Improvement > Components: capacityscheduler, metrics > Reporter: Weiwei Yang > Assignee: Weiwei Yang > Priority: Critical > Attachments: YARN-8213.001.patch, YARN-8213.002.patch, > YARN-8213.003.patch, YARN-8213.004.patch, YARN-8213.005.patch > > > Currently when tune CS performance, it is not that straightforward because > lacking of metrics. Right now we only have \{{QueueMetrics}} which mostly > only tracks queue level resource counters. Propose to add CS metrics to > collect and display more fine-grained perf metrics. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org