[
https://issues.apache.org/jira/browse/AMBARI-10344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-10344:
--------------------------------------
Attachment: AMBARI-10344.patch
> Min/Max/Step/etc from '/recommendations' API should override '/stacks' data
> ---------------------------------------------------------------------------
>
> Key: AMBARI-10344
> URL: https://issues.apache.org/jira/browse/AMBARI-10344
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Fix For: 2.1.0
>
> Attachments: AMBARI-10344.patch
>
>
> Enhanced config {{yarn.nodemanager.resource.memory-mb}} has a maximum value
> of {{268435456 MB}} which comes from the static stack-definition of the
> config. However the real maximum of this config is given by the
> /recommendations call - which calculates it based on the machine's actual
> memory.
> {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" : {
> "max" : "2"
> },
> "yarn.scheduler.maximum-allocation-vcores" : {
> "max" : "2"
> },
> "yarn.nodemanager.resource.memory-mb" : {
> "max" : "2887"
> },
> "yarn.scheduler.minimum-allocation-mb" : {
> "max" : "2048"
> },
> "yarn.nodemanager.resource.cpu-vcores" : {
> "max" : "4"
> },
> "yarn.scheduler.maximum-allocation-mb" : {
> "max" : "2048"
> }
> }
> }
> {code}
> Wherever configs are shown (installer, service-config, host-page,
> add-service, etc.), we need to override the static stack-default
> property_attributes with the /recommendations given property_attributes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
