ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11986) Stack advisor not picking correct reference host consistently
Date Thu, 18 Jun 2015 02:03:00 GMT

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

Srimanth Gunturi commented on AMBARI-11986:
-------------------------------------------

Verified patch on live cluster.
ambari-server stack-advisor tests pass.


> 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)

Mime
View raw message