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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/08/26 21:04:20 UTC
[jira] [Commented] (HADOOP-13552) RetryInvocationHandler logs all
remote exceptions
[ https://issues.apache.org/jira/browse/HADOOP-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439846#comment-15439846 ]
Jason Lowe commented on HADOOP-13552:
-------------------------------------
Looks like this was introduced in HADOOP-13146. Normally logging then throwing the same exception is an anti-pattern since it either logs when it shouldn't (as in this case) or it ends up logging more than once when the ultimate handler of the exception fields it.
> RetryInvocationHandler logs all remote exceptions
> -------------------------------------------------
>
> Key: HADOOP-13552
> URL: https://issues.apache.org/jira/browse/HADOOP-13552
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.8.0
> Reporter: Jason Lowe
> Priority: Blocker
>
> RetryInvocationHandler logs a warning for any exception that it does not retry. There are many exceptions that the client can automatically handle, like FileNotFoundException, UnresolvedPathException, etc., so now every one of these generates a scary looking stack trace as a warning then the program continues normally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org