You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/02/12 15:30:03 UTC
[jira] [Updated] (HADOOP-13611) FileSystem/s3a processDeleteOnExit
to skip the exists() check
[ https://issues.apache.org/jira/browse/HADOOP-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-13611:
------------------------------------
Parent: HADOOP-15220 (was: HADOOP-14831)
> FileSystem/s3a processDeleteOnExit to skip the exists() check
> -------------------------------------------------------------
>
> Key: HADOOP-13611
> URL: https://issues.apache.org/jira/browse/HADOOP-13611
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs, fs/s3
> Affects Versions: 2.7.3
> Reporter: Steve Loughran
> Priority: Trivial
>
> If you look at {{FileSystem.processDeleteOnExit()}}, it does an exists() check for each entry, before calling delete().
> That exists() check is superfluous; on s3 it add an extra 1-4 HTTP GETs
> This could be fixed with a subclass in s3a to avoid it, but as the call is superfluous in *all* filesystems, it could be removed in {{FileSystem}} and so picked up by all object stores.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org