[
https://issues.apache.org/jira/browse/HADOOP-17454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-17454:
------------------------------------
Release Note: S3A bucket existence check is disabled (fs.s3a.bucket.probe
is 0), so there will be no existence check on the bucket during the
S3AFileSystem initialization. The first operation which attempts to interact
with the bucket which will fail if the bucket does not exist. (was: S3A bucket
existence check is disabled (fs.s3a.bucket.probe is 0), so there will be no
existence check on the bucket during the S3AFileSystem initialization. The
first operation will fail if the bucket does not exist.)
> [s3a] Disable bucket existence check - set fs.s3a.bucket.probe to 0
> -------------------------------------------------------------------
>
> Key: HADOOP-17454
> URL: https://issues.apache.org/jira/browse/HADOOP-17454
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.3.0
> Reporter: Gabor Bota
> Assignee: Gabor Bota
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Set the value of fs.s3a.bucket.probe to 0 by default.
> Bucket existence checks are done in the initialization phase of the
> S3AFileSystem. It's not required to run this check: the operation itself will
> fail if the bucket does not exist instead of the check.
> Some points on why do we want to set this to 0:
> * When it's set to 0, bucket existence checks won't be done during
> initialization thus making it faster.
> * Avoid the additional one or two requests on the bucket root, so the user
> does not need rights to read or list that folder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
