[
https://issues.apache.org/jira/browse/HADOOP-15658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578914#comment-16578914
]
Steve Loughran commented on HADOOP-15658:
-----------------------------------------
HADOOP-8635 is unrelated: it allows a FS instance to list files to delete in
shutdown/close(), and also adds a way to cancel them. The issue here is related
to the local FS. As long as the successful write() path always deletes its
files, we can get away with not worrying about using
File.deleteOnExit(localfile), because that only gets invoked on a clean process
halt, doesn't it?
> Memory leak in S3AOutputStream
> ------------------------------
>
> Key: HADOOP-15658
> URL: https://issues.apache.org/jira/browse/HADOOP-15658
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.8.4
> Reporter: Piotr Nowojski
> Priority: Major
>
> S3AOutputStream by calling
> {{org.apache.hadoop.fs.s3a.S3AFileSystem#createTmpFileForWrite}} indirectly
> calls {{java.io.File#deleteOnExit}} and \{{java.io.DeleteOnExitHook}} which
> are known for memory leaking:
>
> [https://bugs.java.com/view_bug.do?bug_id=6664633]
> [https://bugs.java.com/view_bug.do?bug_id=4872014]
>
> Apparently it was even fixed for different component couple of years ago
> https://issues.apache.org/jira/browse/HADOOP-8635 .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
