Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 6 Jan 2017 22:15:58 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13032513.1483695843000.672380.1483740958906@Atlassian.JIRA>
In-Reply-To: <JIRA.13032513.1483695843000@Atlassian.JIRA>
References: <JIRA.13032513.1483695843000@Atlassian.JIRA> <JIRA.13032513.1483695843818@arcas>
Subject: [jira] [Updated] (HIVE-15551) memory leak in directsql for
 mysql+bonecp specific initialization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 06 Jan 2017 22:16:00 -0000


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

Sergey Shelukhin updated HIVE-15551:
------------------------------------
    Summary: memory leak in directsql for mysql+bonecp specific initialization  (was: memory leak in directsql for mysql specific initialization)

> memory leak in directsql for mysql+bonecp specific initialization
> -----------------------------------------------------------------
>
>                 Key: HIVE-15551
>                 URL: https://issues.apache.org/jira/browse/HIVE-15551
>             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
(v6.3.4#6332)