[
https://issues.apache.org/jira/browse/AMBARI-19764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-19764:
-----------------------------------
Status: Patch Available (was: Open)
> yarn.min.container.size is read incorrectly on first load of the Hive config
> page
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-19764
> URL: https://issues.apache.org/jira/browse/AMBARI-19764
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.5.0
> Reporter: Siddharth Seth
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19764.patch
>
>
> The value is read in as 1024, even though min_container_size is 12GB on the
> cluster. Impact: The values for minNodes, maxNodes, minConcurrency,
> maxConcurrency on the UI will be incorrect. User selects an incorrect value
> and the cluster will not start.
> When various llap sliders are moved - the correct value of 12GB is read.
> The stack advisor code needs to be modified to take advantage of AMBARI-19701
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
