hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Hagleitner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10233) Hive on LLAP: Memory manager
Date Fri, 15 May 2015 22:32:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546295#comment-14546295
] 

Gunther Hagleitner commented on HIVE-10233:
-------------------------------------------

In group by: I think the max size you compute via memory decider defines the max hash table
size also. the max memory in the operator is reserved for memory of the jvm/container. so
when memory manager is on you should store the container memory size in max memory of the
operator, but compute the max hashtable size to be "max memory" of the group by desc.

> Hive on LLAP: Memory manager
> ----------------------------
>
>                 Key: HIVE-10233
>                 URL: https://issues.apache.org/jira/browse/HIVE-10233
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>    Affects Versions: llap
>            Reporter: Vikram Dixit K
>            Assignee: Vikram Dixit K
>         Attachments: HIVE-10233-WIP-2.patch, HIVE-10233-WIP-3.patch, HIVE-10233-WIP-4.patch,
HIVE-10233-WIP-5.patch, HIVE-10233-WIP-6.patch
>
>
> We need a memory manager in llap/tez to manage the usage of memory across threads. 



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

Mime
View raw message