[
https://issues.apache.org/jira/browse/HADOOP-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812305#comment-17812305
]
ASF GitHub Bot commented on HADOOP-19049:
-----------------------------------------
steveloughran commented on PR #6488:
URL: https://github.com/apache/hadoop/pull/6488#issuecomment-1916823954
those java links have convinced me; StreamCloser in the jdk does exactly
this.
If you can do a test for this -fine. but it may be too hard to write a test
for...in which case I will merge as is
> Class loader leak caused by StatisticsDataReferenceCleaner thread
> -----------------------------------------------------------------
>
> Key: HADOOP-19049
> URL: https://issues.apache.org/jira/browse/HADOOP-19049
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Affects Versions: 3.3.6
> Reporter: Jia Fan
> Priority: Major
> Labels: pull-request-available
>
> The
> "org.apache.hadoop.fs.FileSystem$Statistics$StatisticsDataReferenceCleaner"
> daemon thread was created by FileSystem.
> This is fine if the thread's context class loader is the system class loader,
> but it's bad if the context class loader is a custom class loader. The
> reference held by this daemon thread means that the class loader can never
> become eligible for GC.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
