hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7718) DFSClient objects created by AbstractFileSystem objects created by FileContext are not closed and results in thread leakage
Date Mon, 02 Feb 2015 19:55:36 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301790#comment-14301790
] 

Colin Patrick McCabe commented on HDFS-7718:
--------------------------------------------

There was some discussion about this on HDFS-3359.  FileContext doesn't have a close method,
unfortunately.  It also tends to rapidly re-create DFSClients.

It seems like we should keep any long-running threads inside {{ClientContext}}, the same way
we do with the socket cache and the short-circuit file descriptor cache. 

> DFSClient objects created by AbstractFileSystem objects created by FileContext are not
closed and results in thread leakage
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7718
>                 URL: https://issues.apache.org/jira/browse/HDFS-7718
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>
> Currently, the {{FileContext}} class used by clients such as (for eg. {{YARNRunner}})
creates a new {{AbstractFilesystem}} object on initialization.. which creates a new {{DFSClient}}
object.. which in turn creates a KeyProvider object.. If Encryption is turned on, and https
is turned on, the keyprovider implementation (the {{KMSClientProvider}}) will create a {{ReloadingX509TrustManager}}
thread per instance... which are never killed and can lead to a thread leak



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message