hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vihang Karajgaonkar (JIRA)" <>
Subject [jira] [Commented] (HIVE-16949) Leak of threads from Get-Input-Paths and Get-Input-Summary thread pool
Date Sun, 27 Aug 2017 18:14:02 GMT


Vihang Karajgaonkar commented on HIVE-16949:

+1 LGTM.

> Leak of threads from Get-Input-Paths and Get-Input-Summary thread pool
> ----------------------------------------------------------------------
>                 Key: HIVE-16949
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Birger Brunswiek
>            Assignee: Sahil Takiar
>         Attachments: HIVE-16949.1.patch
> The commit [20210de|]
which was part of HIVE-15546 [introduced a thread pool|]
which is not shutdown upon completion of its threads. This leads to a leak of threads for
each query which uses more than 1 partition. They are not removed automatically. When queries
spanning multiple partitions are made the number of threads increases and is never reduced.
On my machine hiveserver2 starts to get slower and slower once 10k threads are reached.
> Thread pools only shutdown automatically in special circumstances (see [documentation
section _Finalization_|]).
This is not currently the case for the Get-Input-Paths thread pool. I would add a _pool.shutdown()_
in a finally block just before returning the result to make sure the threads are really shutdown.
> My current workaround is to set {{hive.exec.input.listing.max.threads = 1}}. This prevents
the the thread pool from being spawned [\[1\]|]
> The same issue probably also applies to the [Get-Input-Summary thread pool|].

This message was sent by Atlassian JIRA

View raw message