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 2016/04/04 20:16:26 UTC
[jira] [Resolved] (HADOOP-13000) IPC client can raise
UndeclaredThrowableException during failure handling if maxwait==0
[ https://issues.apache.org/jira/browse/HADOOP-13000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-13000.
-------------------------------------
Resolution: Invalid
log from an old bit of code. It was an interruption. next stack trace for a new app
> IPC client can raise UndeclaredThrowableException during failure handling if maxwait==0
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-13000
> URL: https://issues.apache.org/jira/browse/HADOOP-13000
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.7.1
> Reporter: Steve Loughran
>
> When an IPC falls, it may goes into a retry process, which sleeps via Thread.sleep() .
> If this happens, and the max wait interval is set to 0, then an InterruptedException can trigger in a Thread.sleep() operation. This isn't in the method signatures, so gets wrapped in an UndeclaredThrowable. This isn't an IOE, so all code catching IOEs get confused.
> The original exception is also completely lost.
> Proposed: InterruptedExceptions in the sleep are caught, trigger throwing of the original exception instead
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)