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/06/26 14:25:00 UTC

[jira] [Resolved] (HADOOP-14590) Extend and enhance S3A exception handling

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

Steve Loughran resolved HADOOP-14590.
-------------------------------------
    Resolution: Duplicate

duplicate of HADOOP-14531; couldn't find that when I searched around. 

> Extend and enhance S3A exception handling
> -----------------------------------------
>
>                 Key: HADOOP-14590
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14590
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.1
>            Reporter: Steve Loughran
>
> S3A {{translateException()}} works OK, but we should look at improving it for diagnostics (more details), code (more specific exceptions), and, critically, for meaningful translation of other AWS services including DynamoDB, token services & key management.
> This could be followed by better retry logic, which will be easier ones exception translation is improved. In particular, we may want to hint about which exceptions may be retriable, and which ones are going to be fatal (auth)



--
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