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 2020/01/06 16:00:00 UTC
[jira] [Commented] (HADOOP-16785) Improve wasb and abfs resilience
on double close() calls
[ https://issues.apache.org/jira/browse/HADOOP-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008964#comment-17008964 ]
Steve Loughran commented on HADOOP-16785:
-----------------------------------------
and abfs:
{code}
java.lang.IllegalArgumentException: Self-suppression not permitted
at java.lang.Throwable.addSuppressed(Throwable.java:1072)
at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
at org.apache.commons.io.IOUtils.closeQuietly(IOUtils.java:303)
at org.apache.commons.io.IOUtils.closeQuietly(IOUtils.java:274)
{code}
This is in try-with-resources
{code}
public void close() throws IOException {
try (OutputStream ostream = out) {
flush();
}
}
{code}
hypothesis: flush() and close() are raising the same exception; the attempt to add the close() exception to that of flush() is rejected;
> Improve wasb and abfs resilience on double close() calls
> --------------------------------------------------------
>
> Key: HADOOP-16785
> URL: https://issues.apache.org/jira/browse/HADOOP-16785
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
>
> # if you call write() after the NativeAzureFsOutputStream is closed it throws an NPE ... which isn't always caught by closeQuietly code. It needs to raise an IOE
> # abfs close ops can trigger failures in try-with-resources use
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org