[
https://issues.apache.org/jira/browse/AMBARI-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727338#comment-15727338
]
Hadoop QA commented on AMBARI-19116:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842062/AMBARI-19116.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9556//console
This message is automatically generated.
> Hive2/HiveServer2 (HSI) heap size calculation to be based on LLAP concurrency.
> ------------------------------------------------------------------------------
>
> Key: AMBARI-19116
> URL: https://issues.apache.org/jira/browse/AMBARI-19116
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.1
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19116.patch
>
>
> - Currently, hive2/HiveServer2 (HSI) heap size is ket same as that of
> hive/HiveServer2.
> Required:
> - Hive2/HiveServer2 (HSI) heap size calculations to be based on LLAP
> concurrency.
> {code}
> = min(max(2GB, 400*LLAP concurrency (Tez sessions)), 3/8 * <HS2 host total
> RAM>)
> {code}
> *Side fix:* Also, updated "hive.llap.daemon.queue.name" and
> "hive.server2.tez.default.queues" config values to one of the existing leaf
> queues, in case of HSI being turned on and config values have queue names
> which no more exist. The scenario can happen when, say :
> - HSI was ON and the above 2 configs has queue name 'XYZ'.
> - HSI was then turned off.
> - Capacity Scheduler queues were changed and 'XYZ' queue was deleted.
> - The above configs without this fix will otherwise show stale/non-existing
> queue name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
