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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/02/02 10:33:00 UTC
[jira] [Updated] (HADOOP-17498) Add a MkdirOperation for chained S3
operations during mkdir
[ https://issues.apache.org/jira/browse/HADOOP-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HADOOP-17498:
------------------------------------
Labels: pull-request-available (was: )
> Add a MkdirOperation for chained S3 operations during mkdir
> -----------------------------------------------------------
>
> Key: HADOOP-17498
> URL: https://issues.apache.org/jira/browse/HADOOP-17498
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> on S3A mkdirs is implemented as a walk up the tree looking for any parent dir, exiting fast when found; failing if a file is found.
> Proposed: pull this out into its own MkDir operation with the goals of efficiency, track duration and isolate/test
> * specific callbacks to getFileStatus and createFakeDirectory(key);
> * Move from simple getFileStatus call to probes assuming dir exists before looking for a file: HEAD + path /, LIST path,
> * the probe for a file HEAD path will only succeed in a failure mode where higher cost is a detail
> I think I'd also like to start looking at what we can do with some context tracking/telemetry where something provides an operation ID and ability to attach this to the requests
--
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