ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10593) YARN CPU vCore values returned by not being shown in UI
Date Mon, 20 Apr 2015 11:32:58 GMT

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

Hadoop QA commented on AMBARI-10593:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12726547/AMBARI-10593.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2412//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2412//console

This message is automatically generated.

> YARN CPU vCore values returned by not being shown in UI
> -------------------------------------------------------
>
>                 Key: AMBARI-10593
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10593
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10593.patch, Screen Shot 2015-04-16 at 6.09.53 PM.png
>
>
> The recommendations API returned the following recommendations
> {code}
>             "yarn-site" : {
>               "properties" : {
>                 "yarn.scheduler.minimum-allocation-mb" : "682",
>                 "yarn.scheduler.maximum-allocation-mb" : "2048",
>                 "yarn.nodemanager.resource.cpu-vcores" : "2",
>                 "yarn.nodemanager.resource.memory-mb" : "2048"
>               },
>               "property_attributes" : {
>                 "yarn.scheduler.minimum-allocation-vcores" : {
>                   "maximum" : "2"
>                 },
>                 "yarn.scheduler.maximum-allocation-vcores" : {
>                   "maximum" : "2"
>                 },
>                 "yarn.nodemanager.resource.memory-mb" : {
>                   "maximum" : "2887"
>                 },
>                 "yarn.scheduler.minimum-allocation-mb" : {
>                   "maximum" : "2048"
>                 },
>                 "yarn.nodemanager.resource.cpu-vcores" : {
>                   "maximum" : "4"
>                 },
>                 "yarn.scheduler.maximum-allocation-mb" : {
>                   "maximum" : "2048"
>                 }
>               }
> {code}
> However the UI is not showing the min/max as given in the API (image attached)
> Also, when the value of {{yarn.nodemanager.resource.cpu-vcores}} is changed, the values
of the 2 dependent configs is not updating.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message