hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-11585) Explicitly set pmf.setDetachAllOnCommit on metastore unless configured otherwise
Date Mon, 17 Aug 2015 21:36:45 GMT

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

Sergey Shelukhin commented on HIVE-11585:
-----------------------------------------

There may be implications of that in metastore code... IIRC all the MBlah objects become invalid
when detached, which can be an epic PITA. Fixing this will need some testing.

> Explicitly set pmf.setDetachAllOnCommit on metastore unless configured otherwise
> --------------------------------------------------------------------------------
>
>                 Key: HIVE-11585
>                 URL: https://issues.apache.org/jira/browse/HIVE-11585
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>
> datanucleus.detachAllOnCommit has a default value of false. However, we've observed a
number of objects (especially FieldSchema objects) being retained  that causes us OOM issues
on the metastore. Hive should prefer using a default of datanucleus.detachAllOnCommit as true,
unless otherwise explicitly overridden by users.



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

Mime
View raw message