hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-11355) Hive on tez: memory manager for sort buffers (input/output) and operators
Date Fri, 07 Aug 2015 19:37:45 GMT


Sergey Shelukhin commented on HIVE-11355:

in GBO - why isn't it checking for flushes anymore if memoryNeeded is specified?
createEdgeProperty nit - memoryManagerEnabled is only used in one case block but it is retrieved
for all of them.
dummyStoreOp.setConf(new DummyStoreDesc()); - what is this for?
Invalid configuration could cause OutOfMemory issues at runtime. Configuration "
            + mapJoinsTotalAvailableMemory + " is greater than configured container size:
            + totalAvailableMemory + ". Check your tez/yarn settings");
Will this happen to many people? When the threshold is set to some arbitrary high value to
force map join, this may happen, even though this value will not actually be the table size
in reality. IIRC I saw it in some tests.
To be continued

> Hive on tez: memory manager for sort buffers (input/output) and operators
> -------------------------------------------------------------------------
>                 Key: HIVE-11355
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Tez
>    Affects Versions: 2.0.0
>            Reporter: Vikram Dixit K
>            Assignee: Vikram Dixit K
>         Attachments: HIVE-11355.1.patch, HIVE-11355.2.patch, HIVE-11355.3.patch
> We need to better manage the sort buffer allocations to ensure better performance. Also,
we need to provide configurations to certain operators to stay within memory limits.

This message was sent by Atlassian JIRA

View raw message