You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/04/24 15:07:38 UTC
[jira] [Updated] (AMBARI-10726)
'yarn.scheduler.maximum-allocation-vcores' value should be recommended
[ https://issues.apache.org/jira/browse/AMBARI-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen updated AMBARI-10726:
--------------------------------
Attachment: AMBARI-10726.patch
> 'yarn.scheduler.maximum-allocation-vcores' value should be recommended
> ----------------------------------------------------------------------
>
> Key: AMBARI-10726
> URL: https://issues.apache.org/jira/browse/AMBARI-10726
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.1.0
>
> Attachments: AMBARI-10726.patch
>
>
> {{yarn.scheduler.maximum-allocation-vcores}} value is not being recommended in the /recommendations API. It should be the same as {{yarn.nodemanager.resource.cpu-vcores}}. I see the maximum, but even the value should be provided.
> Current output:
> {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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)