Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 7 Sep 2017 09:24:00 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13004893.1473860912000.48111.1504776240906@Atlassian.JIRA>
In-Reply-To: <JIRA.13004893.1473860912000@Atlassian.JIRA>
References: <JIRA.13004893.1473860912000@Atlassian.JIRA> <JIRA.13004893.1473860912137@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HADOOP-13611) FileSystem/s3a processDeleteOnExit
 to skip the exists() check
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 07 Sep 2017 09:24:09 -0000


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

Steve Loughran updated HADOOP-13611:
------------------------------------
    Priority: Trivial  (was: Minor)

> 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
(v6.4.14#64029)

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