[
https://issues.apache.org/jira/browse/DRILL-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371626#comment-15371626
]
ASF GitHub Bot commented on DRILL-4768:
---------------------------------------
Github user jinfengni commented on the issue:
https://github.com/apache/drill/pull/543
@vkorukanti , thanks for pointing the place it might leaking. I'll revise
the patch.
Agree with @sudheeshkatkam that HiveStoragePlugin may leak connection (I
saw Drill leaked a connection, when HiveStoragePlugin conf is updated each
time). Since @sudheeshkatkam opened DRILL-4774, it would be addressed in
DRILL-4774.
The fix Sudheesh identified is in later version of Hive. Unless we move
Drill's dependency forward, we need find some way to fix leaking for now. Also,
when the hive client call hit tableNotFound / tableNotAccessible error, Drill
does not have to reconnect.
> 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)
