hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-13779) s3a to skip s3 bucket existence check in initialize() for faster creation
Date Fri, 16 Jun 2017 09:55:00 GMT

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

Steve Loughran resolved HADOOP-13779.
    Resolution: Duplicate

Duplicate of HADOOP-13757

> s3a to skip s3 bucket existence check in initialize() for faster creation
> -------------------------------------------------------------------------
>                 Key: HADOOP-13779
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13779
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Rajesh Balamohan
>            Priority: Minor
> The {{verifyBucketExists()}} makes an HTTPS HEAD request of a bucket when creating an
FS, adding an extra HTTPS call of a few hundred millis. (as this is the first call, cost may
be amplified for DNS lookup, thread pool creation, etc, so may appear more expensive).
> If a bucket doesn't exist, the first actual client-initiated operation (get, list, put)
will trigger a failure, so the call could potentially be stripped out.
> # it will complicate failure reporting, if you want to distinguish "unauthed" and "not
found" on a blob from those on a bucket.
> # the fact that the first HTTPS request probably includes first-HTTPS call overhead (pool
creation, DNS, any certificate checking) may make that first call appear more expensive than
it is...those actions would just take place on the first client-initiated call.

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