[
https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-16921:
-------------------------------------
Summary: Take into account reading 'hive.tez.container.size',
'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' &
'tez.am.resource.memory.mb' configs from configurations if they are changed in
current Stack Advisor invocation (was: Yarn minimum container size calculation
problem in stack advisor)
> Take into account reading 'hive.tez.container.size',
> 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb'
> & 'tez.am.resource.memory.mb' configs from configurations if they are changed
> in current Stack Advisor invocation
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-16921
> URL: https://issues.apache.org/jira/browse/AMBARI-16921
> Project: Ambari
> Issue Type: Bug
> Reporter: Daniel Gergely
> Assignee: Daniel Gergely
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16921.patch
>
>
> Stack advisor gets yarn minimum container size property from only the
> "services" input, but does not take into account the already calculated
> configurations.
> As a result memory size for hive interactive server is not correct, so it
> doesn't start.
> 'hive-site/hive.tez.container.size',
> 'yarn-site/yarn.scheduler.minimum-allocation-mb',
> 'yarn-site/yarn.nodemanager.resource.memory-mb' and
> 'tez-interactive-site/tez.am.resource.memory.mb'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
