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 "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2020/04/10 18:15:07 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 ]

Brahma Reddy Battula updated HADOOP-13611:
------------------------------------------
    Target Version/s: 3.4.0  (was: 3.3.0)

Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a blocker.

> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org