[
https://issues.apache.org/jira/browse/HADOOP-14531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063164#comment-16063164
]
Steve Loughran commented on HADOOP-14531:
-----------------------------------------
DDB, STS, KMS all have their own meanings for 404; mapping to FNFE isn't
appropriate for them.
Proposed: use service information in the AWS exception fields to forward
translation to a service-specific translator, if present. If this returns an
explicit exception, throw it. Otherwise fall back to the main one.
Testing easiest if we can just create the exceptions from stack traces in JIRAs
> Improve S3A error handling & reporting
> --------------------------------------
>
> Key: HADOOP-14531
> URL: https://issues.apache.org/jira/browse/HADOOP-14531
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 2.8.1
> Reporter: Steve Loughran
>
> Improve S3a error handling and reporting
> this includes
> # looking at error codes and translating to more specific exceptions
> # better retry logic where present
> # adding retry logic where not present
> # more diagnostics in exceptions
> # docs
> Overall goals
> * things that can be retried and will go away are retried for a bit
> * things that don't go away when retried failfast (302, no auth, unknown
> host, connection refused)
> * meaningful exceptions are built in translate exception
> * diagnostics are included, where possible
> * our troubleshooting docs are expanded with new failures we encounter
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
