[
https://issues.apache.org/jira/browse/HADOOP-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239150#comment-14239150
]
Hadoop QA commented on HADOOP-11368:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685960/HADOOP-11368.1.patch
against trunk revision db73cc9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 65 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5204//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5204//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5204//console
This message is automatically generated.
> Fix OutOfMemory caused due to leaked trustStore reloader thread in
> KMSClientProvider
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-11368
> URL: https://issues.apache.org/jira/browse/HADOOP-11368
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 2.5.0
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: HADOOP-11368.1.patch
>
>
> When a {{KMSClientProvider}} is initialized in _ssl_ mode, It initializes a
> {{SSLFactory}} object. This in-turn creates an instance of
> {{ReloadingX509TrustManager}} which, on initialization, starts a trust store
> reloader thread.
> It is noticed that over time, as a number of short lived
> {{KMSClientProvider}} instances are created and destroyed, the trust store
> manager threads are not interrupted/killed and remain in TIMED_WAITING state.
> A Thread dump shows multiple:
> {noformat}
> "Truststore reloader thread" daemon prio=10 tid=0x00007fb1cf942800 nid=0x4e99
> waiting on condition [0x00007fb0485f5000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.run(ReloadingX509TrustManager.java:189)
> at java.lang.Thread.run(Thread.java:662)
> Locked ownable synchronizers:
> - None
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
