hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10309) S3 block filesystem should more aggressively delete temporary files
Date Tue, 27 Jan 2015 10:27:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-10309:
------------------------------------
    Status: Patch Available  (was: Open)

> S3 block filesystem should more aggressively delete temporary files
> -------------------------------------------------------------------
>
>                 Key: HADOOP-10309
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10309
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 2.6.0
>            Reporter: Joe Kelley
>            Priority: Minor
>         Attachments: HADOOP-10309.patch
>
>
> The S3 FileSystem reading implementation downloads block files into a configurable temporary
directory. deleteOnExit() is called on these files, so they are deleted when the JVM exits.
> However, JVM reuse can lead to JVMs that stick around for a very long time. This can
cause these temporary files to build up indefinitely and, in the worst case, fill up the local
directory.
> After a block file has been read, there is no reason to keep it around. It should be
deleted.
> Writing to the S3 FileSystem already has this behavior; after a temporary block file
is written and uploaded to S3, it is deleted immediately; there is no need to wait for the
JVM to exit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message