You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Íñigo Goiri (JIRA)" <ji...@apache.org> on 2018/06/28 16:39:00 UTC
[jira] [Commented] (YARN-7690) Expose reserved Memory/Vcores of
Node Manager at WebUI
[ https://issues.apache.org/jira/browse/YARN-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526505#comment-16526505 ]
Íñigo Goiri commented on YARN-7690:
-----------------------------------
Thanks [~jutia] for the patch.
Can you add unit tests for this?
A couple screenshots would also be helpful.
> Expose reserved Memory/Vcores of Node Manager at WebUI
> ------------------------------------------------------
>
> Key: YARN-7690
> URL: https://issues.apache.org/jira/browse/YARN-7690
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: webapp
> Reporter: tianjuan
> Assignee: tianjuan
> Priority: Major
> Attachments: YARN-7690.patch
>
>
> Now only total reserved memory/Vcores are exposed at RM Web UI, reserved memory/Vcores of a single nodemanager is hard to find out. It confuses users that they observe that there are available memory/Vcores at nodes page, but their jobs are stuck and waiting for resource to be allocated. It is helpful for debug to expose reserved memory/Vcores of every single nodemanager, and memory/Vcores that can be allocated (unallocated minus reserved).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org