[
https://issues.apache.org/jira/browse/AMBARI-11515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srimanth Gunturi updated AMBARI-11515:
--------------------------------------
Summary: Configs: increasing "Memory allocated for all YARN containers on a
node" slightly makes "Maximum Container Size" go out of range (was: Configs:
increasing "YARN > Memory > Node > Memory allocated for all YARN containers on
a node" slightly makes "Maximum Container Size" go out of range)
> 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
>
>
> 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)
