You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2017/08/11 23:31:00 UTC

[jira] [Assigned] (HIVE-17304) ThreadMXBean based memory allocation monitory for hash table loader

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

Prasanth Jayachandran reassigned HIVE-17304:
--------------------------------------------


> ThreadMXBean based memory allocation monitory for hash table loader
> -------------------------------------------------------------------
>
>                 Key: HIVE-17304
>                 URL: https://issues.apache.org/jira/browse/HIVE-17304
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>
> Hash table memory monitoring is based on java data model which can be unreliable because of various reasons (wrong object size estimation, adding new variables to any class without accounting its size for memory monitoring, etc.). We can use allocation size per thread that is provided by ThreadMXBean and fallback to DataModel in case if JDK doesn't support thread based allocations. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)