[ https://issues.apache.org/jira/browse/HADOOP-13130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292847#comment-15292847 ]
Chris Nauroth commented on HADOOP-13130: ---------------------------------------- Patch 012 looks good. Thanks for digging out more details about those errors. We'll need a minor rebase now that HADOOP-13183 has been committed, and the Findbugs warning is worth fixing. > s3a failures can surface as RTEs, not IOEs > ------------------------------------------ > > Key: HADOOP-13130 > URL: https://issues.apache.org/jira/browse/HADOOP-13130 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 2.7.2 > Reporter: Steve Loughran > Assignee: Steve Loughran > Attachments: HADOOP-13130-001.patch, HADOOP-13130-002.patch, > HADOOP-13130-002.patch, HADOOP-13130-003.patch, HADOOP-13130-004.patch, > HADOOP-13130-005.patch, HADOOP-13130-branch-2-006.patch, > HADOOP-13130-branch-2-007.patch, HADOOP-13130-branch-2-008.patch, > HADOOP-13130-branch-2-009.patch, HADOOP-13130-branch-2-010.patch, > HADOOP-13130-branch-2-011.patch, HADOOP-13130-branch-2-012.patch > > > S3A failures happening in the AWS library surface as > {{AmazonClientException}} derivatives, rather than IOEs. As the amazon > exceptions are runtime exceptions, any code which catches IOEs for error > handling breaks. > The fix will be to catch and wrap. The hard thing will be to wrap it with > meaningful exceptions rather than a generic IOE. Furthermore, if anyone has > been catching AWS exceptions, they are going to be disappointed. That means > that fixing this situation could be considered "incompatible" —but only for > code which contains assumptions about the underlying FS and the exceptions > they raise. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org