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] [Updated] (AMBARI-4999) Ambari should allow at least 3 yarn containers on a one-node installation
Date Fri, 07 Mar 2014 21:30:43 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Srimanth Gunturi updated AMBARI-4999:
-------------------------------------

    Attachment: AMBARI-4999.patch

Review at https://reviews.apache.org/r/18923/

> Ambari should allow at least 3 yarn containers on a one-node installation
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-4999
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4999
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4999.patch
>
>
> Ambari UI calculates ram-per-container as a fraction. 
> YARN scheduler's minimum memory is Math.round(ram-per-container), while the maximum memory
is Math.round(number-of-containers * ram-percontainer). 
> The problem is that for some fractional values, 3*Math.round(fraction) > Math.round(3*fraction).
(Ex: Take value 1.7). Because of that less number of containers can actually be started, as
the value slightly goes over the maximum.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message