Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 11 Jul 2016 16:02:11 +0000 (UTC)
From: "Jinfeng Ni (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12987348.1467850978000.78859.1468252931166@Atlassian.JIRA>
In-Reply-To: <JIRA.12987348.1467850978000@Atlassian.JIRA>
References: <JIRA.12987348.1467850978000@Atlassian.JIRA> <JIRA.12987348.1467850978275@arcas>
Subject: [jira] [Assigned] (DRILL-4768) Drill may leak hive meta store
 connection if hive meta store client call hits error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Jul 2016 16:02:17 -0000


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

Jinfeng Ni reassigned DRILL-4768:
---------------------------------

    Assignee: Jinfeng Ni

> Drill may leak hive meta store connection if hive meta store client call hits error
> -----------------------------------------------------------------------------------
>
>                 Key: DRILL-4768
>                 URL: https://issues.apache.org/jira/browse/DRILL-4768
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Hive
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>
> We are seeing one drillbit creates hundreds of connections to hive meta store. This indicates that drill is leaking those connection, and did not close those connections properly. When such leaking happens, it may prevent other applications from connecting to hive meta store. 
> It seems one cause of leaking connection happens when hive meta store client call hits exception. 
>  


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