[
https://issues.apache.org/jira/browse/DRILL-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371089#comment-15371089
]
Jinfeng Ni commented on DRILL-4768:
-----------------------------------
The cause of leaking connection is Drill will call reconnect(), whenever the
hive meta store client call throws TException. This includes the case when
"table not found error", or " table not allowed to be accessed", when the
connection is still alive. In such cases, if we call reconnect(), then the
previous connection will be leaked.
> 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)
