hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-20656) Map aggregation memory configs are too aggressive
Date Wed, 27 Feb 2019 22:23:00 GMT

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

Prasanth Jayachandran updated HIVE-20656:
-----------------------------------------
    Status: Patch Available  (was: Open)

> Map aggregation memory configs are too aggressive
> -------------------------------------------------
>
>                 Key: HIVE-20656
>                 URL: https://issues.apache.org/jira/browse/HIVE-20656
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 3.2.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>         Attachments: HIVE-20656.1.patch
>
>
> The defaults for the following configs seems to be too aggressive. In java this can easily
lead to several full GC pauses whose memory cannot be reclaimed.
> {code:java}
> HIVEMAPAGGRHASHMEMORY("hive.map.aggr.hash.percentmemory", (float) 0.99,
>     "Portion of total memory to be used by map-side group aggregation hash table"),
> HIVEMAPAGGRMEMORYTHRESHOLD("hive.map.aggr.hash.force.flush.memory.threshold", (float)
0.9,
>     "The max memory to be used by map-side group aggregation hash table.\n" +
>     "If the memory usage is higher than this number, force to flush data"),{code}
>  
> We can be little bit conservative for these configs to avoid getting into GC pause. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message