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-11515) Configs: increasing "Memory allocated for all YARN containers on a node" slightly makes "Maximum Container Size" go out of range
Date Thu, 28 May 2015 22:05:17 GMT

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

Srimanth Gunturi commented on AMBARI-11515:
-------------------------------------------

So every config has a 'recommended value' and a 'minimum' and 'maximum' value. 

{{yarn.nodemanager.resource.memory-mb}} changes the 'maximum' value of {{yarn.scheduler.maximum-allocation-mb}}
and {{yarn.scheduler.minimum-allocation-mb}}. The problem was that {{yarn.nodemanager.resource.memory-mb}}
value was being calculated even when caller's latest value was being provided. So when caller
changed from 2048 to 2560, the maximum was still being set to 2048.

The fix was to use the caller's latest value if available.

> Configs: increasing "Memory allocated for all YARN containers on a node" slightly makes
"Maximum Container Size" go out of range
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11515
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11515
>             Project: Ambari
>          Issue Type: Bug
>          Components: contrib
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11515.patch
>
>
> When I increased "YARN > Memory > Node > Memory allocated for all YARN containers
on a node" slightly (from 2000 to 2250MB, going one notch up on the slider control) , "Maximum
Container Size" went out of bounds and turned into Edit mode.
> This might be per the spec from the YARN team, but it's kind of weird that any slight
change causes dependent to go out of range.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message