[ https://issues.apache.org/jira/browse/HDFS-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301862#comment-14301862 ]
Hadoop QA commented on HDFS-7718: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12695994/HDFS-7718.1.patch against trunk revision 52575ff. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 6 new or modified test files. {color:red}-1 javac{color:red}. The patch appears to cause the build to fail. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9398//console This message is automatically generated. > 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 > Attachments: HDFS-7718.1.patch > > > 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)