hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <>
Subject [jira] [Commented] (HIVE-4501) HS2 memory leak - FileSystem objects in FileSystem.CACHE
Date Tue, 01 Oct 2013 04:59:26 GMT


Konstantin Boudnik commented on HIVE-4501:

bq. This is not the case, same thread can get used for another session
Are you saying that the same FS ref. can be used across UGIs? If so, It looks like a nice
big hole to me ;) The call for the close of FS is done at the point where the particular UGI's
session is getting finished and all its resources are let go, e.g. operation handlers, metastore,
etc. I am not sure if I follow your comment. Could you please elaborate?

> HS2 memory leak - FileSystem objects in FileSystem.CACHE
> --------------------------------------------------------
>                 Key: HIVE-4501
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 0.11.0
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>            Priority: Critical
>         Attachments: HIVE-4501.1.patch, HIVE-4501.1.patch, HIVE-4501.1.patch, HIVE-4501.trunk.patch
> org.apache.hadoop.fs.FileSystem objects are getting accumulated in FileSystem.CACHE,
with HS2 in unsecure mode.
> As a workaround, it is possible to set fs.hdfs.impl.disable.cache and fs.file.impl.disable.cache
to true.
> Users should not have to bother with this extra configuration. 
> As a workaround disable impersonation by setting hive.server2.enable.doAs to false.

This message was sent by Atlassian JIRA

View raw message