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 "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2014/01/13 23:15:57 UTC
[jira] [Commented] (HADOOP-10106) Incorrect thread name in RPC log
messages
[ https://issues.apache.org/jira/browse/HADOOP-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870059#comment-13870059 ]
Suresh Srinivas commented on HADOOP-10106:
------------------------------------------
[~mingma], I have added you as a contributor and assigned the jira to you.
> Incorrect thread name in RPC log messages
> -----------------------------------------
>
> Key: HADOOP-10106
> URL: https://issues.apache.org/jira/browse/HADOOP-10106
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Ming Ma
> Assignee: Ming Ma
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: hadoop_10106_trunk.patch, hadoop_10106_trunk_2.patch
>
>
> INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8020: readAndProcess from client 10.115.201.46 threw exception org.apache.hadoop.ipc.RpcServerException: Unknown out of band call #-2147483647
> This is thrown by a reader thread, so the message should be like
> INFO org.apache.hadoop.ipc.Server: Socket Reader #1 for port 8020: readAndProcess from client 10.115.201.46 threw exception org.apache.hadoop.ipc.RpcServerException: Unknown out of band call #-2147483647
> Another example is Responder.processResponse, which can also be called by handler thread. When that happend, the thread name should be the handler thread, not the responder thread.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)