hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-15551) memory leak in directsql for mysql specific initialization
Date Fri, 06 Jan 2017 22:14:58 GMT


Sergey Shelukhin commented on HIVE-15551:

[~thejas] fyi, may also affect HS2; if you see some OOMs/etc.

> memory leak in directsql for mysql specific initialization
> ----------------------------------------------------------
>                 Key: HIVE-15551
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.13.0
>            Reporter: Xiaomin Zhang
>            Assignee: Xiaomin Zhang
>         Attachments: HIVE-15551.patch.txt
> We observed HMS memory leak when directsql is enabled for MySQL metastore DB.  
> The affected code is in the method MetaStoreDirecdtSql.executeNoResult():
> ((Connection)jdoConn.getNativeConnection()).createStatement().execute(queryText);
> The statement object (from createStatement()) is unfortunately referenced in the Connection
object.  Although close() is called on the Connection object  in finally block, the BoneCP
just moves it to a freeConnection list. Hence, statement object never get chances to be closed.
> The leaked statement object is not huge (~1KB as observed in memory analyzer). However
long running Hive Metastore Server is very likely ended up with bad performance doing frequent
garbage collection.

This message was sent by Atlassian JIRA

View raw message