[
https://issues.apache.org/jira/browse/HADOOP-17454?focusedWorklogId=531158&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-531158
]
ASF GitHub Bot logged work on HADOOP-17454:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Jan/21 12:29
Start Date: 05/Jan/21 12:29
Worklog Time Spent: 10m
Work Description: steveloughran edited a comment on pull request #2593:
URL: https://github.com/apache/hadoop/pull/2593#issuecomment-754605704
+1 pending successful Yetus build. I've turned off existence checks for a
long time and makes things faster, especially creation of a new FS instance in
test suites.
Do update the release notes though, to say "you'll get told of
missing/unreadable bucket on first operation against it".
Test failure is going to be related to directory marker retention and/or
metric counting.
Could you file a JIRA, assign to me and include the specific test settings
you were using?
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 531158)
Time Spent: 50m (was: 40m)
> [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: 50m
> 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
