[
https://issues.apache.org/jira/browse/YARN-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417883#comment-16417883
]
genericqa commented on YARN-7690:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} YARN-7690 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-7690 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12903982/YARN-7690.patch |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/20127/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> expose reserved memory/Vcores of nodemanager at webUI
> ------------------------------------------------------
>
> Key: YARN-7690
> URL: https://issues.apache.org/jira/browse/YARN-7690
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: webapp
> Reporter: tianjuan
> Priority: Major
> Attachments: YARN-7690.patch
>
>
> now only total reserved memory/Vcores are exposed at RM webUI, reserved
> memory/Vcores of a single nodemanager is hard to find out. it confuses users
> that they obeserve that there are available memory/Vcores at nodes page, but
> their jobs are stuck and waiting for resouce to be allocated. It is helpful
> for bedug 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
