hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13130) s3a failures can surface as RTEs, not IOEs
Date Fri, 20 May 2016 15:29:13 GMT

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

Steve Loughran updated HADOOP-13130:
    Attachment: HADOOP-13130-branch-2-014.patch

Patch 014: sync up with branch-2

* modify {{TestS3AAWSCredentialsProvider}} to (a) force an auth exception throw an {{ls /}},
and (b) fail if nothing gets thrown. That was actuallly a part of HADOOP-12723 which broke
with HADOOP-13058.
* Have those tests look for the relevant translated exceptions
* make sure that {{S3AFilesystem.initialize()}} has all amazon exceptions caught and translated.
I can't see any codepath which *currently* leads to this, but all it would take would be another
bit of setup code or some change in the AWS library. This hardens the code against such a

> s3a failures can surface as RTEs, not IOEs
> ------------------------------------------
>                 Key: HADOOP-13130
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13130
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.7.2
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-13130-001.patch, HADOOP-13130-002.patch, HADOOP-13130-002.patch,
HADOOP-13130-003.patch, HADOOP-13130-004.patch, HADOOP-13130-005.patch, HADOOP-13130-branch-2-006.patch,
HADOOP-13130-branch-2-007.patch, HADOOP-13130-branch-2-008.patch, HADOOP-13130-branch-2-009.patch,
HADOOP-13130-branch-2-010.patch, HADOOP-13130-branch-2-011.patch, HADOOP-13130-branch-2-012.patch,
HADOOP-13130-branch-2-013.patch, HADOOP-13130-branch-2-014.patch
> S3A failures happening in the AWS library surface as {{AmazonClientException}} derivatives,
rather than IOEs. As the amazon exceptions are runtime exceptions, any code which catches
IOEs for error handling breaks.
> The fix will be to catch and wrap. The hard thing will be to wrap it with meaningful
exceptions rather than a generic IOE. Furthermore, if anyone has been catching AWS exceptions,
they are going to be disappointed. That means that fixing this situation could be considered
"incompatible" —but only for code which contains assumptions about the underlying FS and
the exceptions they raise.

This message was sent by Atlassian JIRA

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

View raw message