[
https://issues.apache.org/jira/browse/HADOOP-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615673#comment-17615673
]
ASF GitHub Bot commented on HADOOP-18476:
-----------------------------------------
steveloughran commented on code in PR #4966:
URL: https://github.com/apache/hadoop/pull/4966#discussion_r992153111
##########
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3A.java:
##########
@@ -54,4 +55,13 @@ public String toString() {
sb.append('}');
return sb.toString();
}
+
+ /**
+ * Close the file system; the FileContext API doesn't have an explicit close.
+ */
+ @Override
+ protected void finalize() throws Throwable {
Review Comment:
one fix would be for FileContext to be closeable and so trigger cleanups
without hoping finalize() gets called, especially as GC is triggered by heap
use, and i don't know if thread count does that
> Abfs and S3A FileContext bindings to close wrapped filesystems in finalizer
> ---------------------------------------------------------------------------
>
> Key: HADOOP-18476
> URL: https://issues.apache.org/jira/browse/HADOOP-18476
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure, fs/s3
> Affects Versions: 3.3.4
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
> Labels: pull-request-available
>
> if you use the FileContext APIs to talk to abfs or s3a, it creates a new
> wrapped FileSystem implementation, and, because there is no close() call,
> never cleans up.
> proposed: add finalizers for these two classes, which we know create helper
> threads, especially if plugins are added
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
