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 "Gabor Bota (Jira)" <ji...@apache.org> on 2021/01/05 10:39:00 UTC
[jira] [Updated] (HADOOP-17454) [s3a] Disable bucket existence
check - set fs.s3a.bucket.probe to 0
[ https://issues.apache.org/jira/browse/HADOOP-17454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Bota updated HADOOP-17454:
--------------------------------
Affects Version/s: 3.3.0
> [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
>
> Set the value of fs.s3a.bucket.probe to 0 in the code-default.xml.
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org