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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/07/13 18:43:00 UTC

[jira] [Commented] (HADOOP-13757) Remove verifyBuckets overhead in S3AFileSystem::initialize()

    [ https://issues.apache.org/jira/browse/HADOOP-13757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086195#comment-16086195 ] 

Steve Loughran commented on HADOOP-13757:
-----------------------------------------

It does do a fast check that connectivity is up, and with s3guard there'll be other init actions going on...

> Remove verifyBuckets overhead in S3AFileSystem::initialize()
> ------------------------------------------------------------
>
>                 Key: HADOOP-13757
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13757
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Rajesh Balamohan
>            Priority: Minor
>
> {{S3AFileSystem.initialize()}} invokes verifyBuckets, but in case the bucket does not exist and gets a 403 error message, it ends up returning {{true}} for {{s3.doesBucketExists(bucketName}}.  In that aspect,  verifyBuckets() is an unnecessary call during initialization. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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