[
https://issues.apache.org/jira/browse/AMBARI-11986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591223#comment-14591223
]
Hudson commented on AMBARI-11986:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #66 (See
[https://builds.apache.org/job/Ambari-branch-2.1/66/])
AMBARI-11986. Stack advisor not picking correct reference host consistently
(srimanth) (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98f6ac0844f700e270ce1a3f7a5b8c7274b3717c)
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
> Stack advisor not picking correct reference host consistently
> -------------------------------------------------------------
>
> Key: AMBARI-11986
> URL: https://issues.apache.org/jira/browse/AMBARI-11986
> Project: Ambari
> Issue Type: Bug
> Components: contrib
> Affects Versions: 2.1.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11986.patch
>
>
> If a cluster had 100 hosts where first host had 60GB ram and rest of hosts
> had 3GB ram. The stack-advisor code picks the first host (60GB ram) for some
> calculations (like 'ramPerContainer'), and then picks host with minimum ram
> (3GB ram) for 'yarn.scheduler.minimum-allocation-mb'.
> Due to this, the {{yarn.scheduler.minimum-allocation-mb}} is greater than
> {{yarn.scheduler.maximum-allocation-mb}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
