[
https://issues.apache.org/jira/browse/HADOOP-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224845#comment-13224845
]
Hudson commented on HADOOP-7358:
--------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #664 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/664/])
HADOOP-7358. Merge r1205697 from trunk to 0.23 (Revision 1298207)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1298207
Files :
*
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> Improve log levels when exceptions caught in RPC handler
> --------------------------------------------------------
>
> Key: HADOOP-7358
> URL: https://issues.apache.org/jira/browse/HADOOP-7358
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HADOOP-7358.trunk.patch, hadoop-7358.txt
>
>
> When a server implementation throws an exception handling an RPC, the Handler
> thread catches it and logs it before responding with the exception over the
> IPC channel. This is currently done at INFO level.
> I'd like to propose that, if the exception is an unchecked exception, it
> should be logged at WARN level instead. This can help alert operators when
> they might be hitting some kind of bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
