[
https://issues.apache.org/jira/browse/HADOOP-13857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715291#comment-15715291
]
Steve Loughran commented on HADOOP-13857:
-----------------------------------------
One issue: should all AbortedExceptions be uprated to interruptedExceptions?
HADOOP-13811 hints at other ways in which interruptions may surface. However,
looking for specific error texts is dangerous and brittle
> S3AUtils.translateException to map (wrapped) InterruptedExceptions to
> InterruptedIOEs
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-13857
> URL: https://issues.apache.org/jira/browse/HADOOP-13857
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> Currently {{S3AUtils.translateException}} doesn't recognise interruptions; it
> just sees an AmazonClientException chain which is then relayed up.
> Proposed: look for an {{InterruptedIOException}} at the base of the chain of
> exceptions, map it to an {{InterruptedIOException}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
