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 "Chris Nauroth (JIRA)" <ji...@apache.org> on 2016/10/04 05:55:20 UTC

[jira] [Updated] (HADOOP-13674) S3A can provide a more detailed error message when accessing a bucket through an incorrect S3 endpoint.

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

Chris Nauroth updated HADOOP-13674:
-----------------------------------
    Attachment: HADOOP-13674-branch-2.001.patch

I'm attaching patch 001.  Summary:

* Add specific exception translation logic for an HTTP 301 response.  Include the recommended S3 endpoint and a hint to check {{fs.s3a.endpoint}} in the exception message.
* Update example error in documentation to show that the error message contains the recommended endpoint.
* Introduce a new unit test suite, {{TestS3AExceptionTranslation}}.  This consists of tests refactored out of {{ITestS3AFailureHandling}} that didn't really have a dependency on the S3 service, a new test for an HTTP 301 response, and several other tests for HTTP status codes that weren't already covered, like 403, 410 and 416.


> S3A can provide a more detailed error message when accessing a bucket through an incorrect S3 endpoint.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-13674
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13674
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: HADOOP-13674-branch-2.001.patch
>
>
> When accessing the S3 service through a region-specific endpoint, the bucket must be located in that region.  If the client attempts to access a bucket that is not located in that region, then the service replies with a 301 redirect and the correct region endpoint.  However, the exception thrown by S3A does not include the correct endpoint.  If we included that information in the exception, it would make it easier for users to diagnose and fix incorrect configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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