hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HADOOP-17498) Add a MkdirOperation for chained S3 operations during mkdir
Date Sat, 24 Apr 2021 17:02:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-17498?focusedWorklogId=588312&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-588312

ASF GitHub Bot logged work on HADOOP-17498:

                Author: ASF GitHub Bot
            Created on: 24/Apr/21 17:01
            Start Date: 24/Apr/21 17:01
    Worklog Time Spent: 10m 
      Work Description: steveloughran closed pull request #2671:
URL: https://github.com/apache/hadoop/pull/2671


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 588312)
    Time Spent: 1.5h  (was: 1h 20m)

> 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: 1.5h
>  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

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

View raw message