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

Jim Brennan commented on YARN-10450:
------------------------------------

Checkstyle issue:
{noformat}
./hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ClusterMetrics.java:54:
  @Metric("Memory Utilization") MutableGaugeLong utilizedMB;:50: Variable 
'utilizedMB' must be private and have accessor methods. [VisibilityModifier]
./hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ClusterMetrics.java:55:
  @Metric("Vcore Utilization") MutableGaugeLong utilizedVirtualCores;:49: 
Variable 'utilizedVirtualCores' must be private and have accessor methods. 
[VisibilityModifier]
{noformat}
The new metrics are set up just like existing ones in this file, so I am not 
going to try to fix this.

I think the unit test failures are unrelated to this change.  They are passing 
for me locally.


> Add cpu and memory utilization per node and cluster-wide metrics
> ----------------------------------------------------------------
>
>                 Key: YARN-10450
>                 URL: https://issues.apache.org/jira/browse/YARN-10450
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 3.3.1
>            Reporter: Jim Brennan
>            Assignee: Jim Brennan
>            Priority: Minor
>         Attachments: NodesPage.png, YARN-10450.001.patch, YARN-10450.002.patch
>
>
> Add metrics to show actual cpu and memory utilization for each node and 
> aggregated for the entire cluster.  This is information is already passed 
> from NM to RM in the node status update.
> We have been running with this internally for quite a while and found it 
> useful to be able to quickly see the actual cpu/memory utilization on the 
> node/cluster.  It's especially useful if some form of overcommit is used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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