ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapan Shridhar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16942) 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.
Date Sat, 28 May 2016 02:15:13 GMT

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

Swapan Shridhar updated AMBARI-16942:
-------------------------------------
    Status: Patch Available  (was: In Progress)

> 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-16942
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16942
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16942.patch
>
>
> - While doing Hive Server interactive's LLAP related calculations, take into account
reading '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'
if they are changed in current Stack Advisor invocation. Otherwise read from services array.



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

Mime
View raw message