[
https://issues.apache.org/jira/browse/HADOOP-13811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932838#comment-15932838
]
Steve Loughran commented on HADOOP-13811:
-----------------------------------------
Looking at the AWS SDK,
1. {{AbortedException}} is only ever raised on a thread interrupt; it could be
translated
2. that log that [~fabbri] saw, "Unable to close response InputStream ..." is
just a log @ error of the exception raised when the XML parser closes the input
stream: it's not the actual point where something was thrown, but just the
errors in the close() call. The stuff we'd log @ debug in our own code.
I propose translateException has a special handler for an aborted exception at
the base of the call chain; if thrown raises in InterrupteIOE. Or we actually
set the interrupted bit on the thread again? That'd be purer, but more of a
change in the system operation, potentially
> s3a: getFileStatus fails with com.amazonaws.AmazonClientException: Failed to
> sanitize XML document destined for handler class
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13811
> URL: https://issues.apache.org/jira/browse/HADOOP-13811
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0, 2.7.3
> Reporter: Steve Loughran
>
> Sometimes, occasionally, getFileStatus() fails with a stack trace starting
> with {{com.amazonaws.AmazonClientException: Failed to sanitize XML document
> destined for handler class}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
