hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navis (JIRA)" <>
Subject [jira] [Commented] (HIVE-3969) Session state for hive server should be cleanup
Date Mon, 04 Feb 2013 00:52:12 GMT


Navis commented on HIVE-3969:

If a client add jar files for initializing, hive server makes a new classloader and attach
it to thread as a context loader. Cause hive server uses thread pool and there is no cleanup
for threads, number of class loader increases constantly, which can make possibly a memory
issue. And also it prevents using newer library containing class with same name, which means
hive server should be restarted for reflecting new library.

But cause current hive server cannot sustain consistent session between invocations from single
client, this patch can induce other problems, which makes it incomplete. I know HiveServer2
is already on a way to be committed. Would it be better to fix session problems in hiveserver
also or to make it deprecated quickly after hiveserver2 is committed? I don't know. 
> Session state for hive server should be cleanup
> -----------------------------------------------
>                 Key: HIVE-3969
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Server Infrastructure
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Trivial
>         Attachments: HIVE-3969.D8325.1.patch
> Currently "add jar" command by clients are adding child ClassLoader to worker thread
cumulatively, causing various problems.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message