hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-9359) Export of a large table causes OOM in Metastore and Client
Date Tue, 27 Jan 2015 00:26:35 GMT

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

Sushanth Sowmyan updated HIVE-9359:
-----------------------------------
    Fix Version/s: 1.0.0

> Export of a large table causes OOM in Metastore and Client
> ----------------------------------------------------------
>
>                 Key: HIVE-9359
>                 URL: https://issues.apache.org/jira/browse/HIVE-9359
>             Project: Hive
>          Issue Type: Bug
>          Components: Import/Export, Metastore
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>             Fix For: 0.15.0, 1.0.0
>
>         Attachments: HIVE-9359.2.patch, HIVE-9359.patch
>
>
> Running hive export on a table with a large number of partitions winds up making the
metastore and client run out of memory. The number of places we wind up having a copy of the
entire partitions object wind up being as follows:
> Metastore
>    * (temporarily) Metastore MPartition objects
>    * List<Partition> that gets persisted before sending to thrift
>    * thrift copy of all of those partitions
> Client side
>    * thrift copy of partitions
>    * deepcopy of above to create List<Partition> objects
>    * JSONObject that contains all of those above partition objects
>    * List<ReadEntity> which each encapsulates the aforesaid partition objects.
> This memory usage needs to be drastically reduced.



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

Mime
View raw message