[
https://issues.apache.org/jira/browse/YARN-10450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212632#comment-17212632
]
Eric Badger commented on YARN-10450:
------------------------------------
The patch itself looks good to me. However, I'm wondering if "Mem Utilization"
is the correct phrase to convey what we mean. To me this means "Mem Used" /
"Mem Avail". But in this case it's the actual utilization of the node. And "Mem
Used" isn't really the actual memory that's being used. It's the memory that is
allocated to that node via YARN.
[~Jim_Brennan], [~epayne] do you have any thoughts on making this terminology a
little more clear on the UI?
> 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
