[
https://issues.apache.org/jira/browse/HADOOP-17335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235460#comment-17235460
]
Steve Loughran commented on HADOOP-17335:
-----------------------------------------
Also managed to create an InterruptedIOException and RejectedExecutionException
(submitting to the executor pool as it is terminated)
The interrupted one makes the most sense, the XML parser the least intuitive.
Not sure what to do here
I think internally the SDK is not picking up that the stream is closed and is
still trying to close the stream gracefully.
Looking @ the AWS code, the error is coming from the handler of a failure in
the stream close(); it's overreacting to the inner exception
{code}
try {
inputStream.close();
} catch (IOException e) {
if (log.isErrorEnabled()) {
log.error("Unable to close response InputStream after
failure sanitizing XML document", e);
}
}
{code}
It should be treating a SocketException in close() as unimportant. So let's not
worry about that. it's an overreaction in the log, but not our log.
> s3a listing operation will fail in async prefetch if fs closed
> --------------------------------------------------------------
>
> Key: HADOOP-17335
> URL: https://issues.apache.org/jira/browse/HADOOP-17335
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Mukund Thakur
> Priority: Minor
>
> The async prefetch logic in the S3A listing code gets into trouble if the FS
> closed and there was an async listing in progress.
> In this situation we should think about recognising and converting into some
> FS-is-closed exception
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
