hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10106) Incorrect thread name in RPC log messages
Date Sat, 07 Dec 2013 01:29:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841989#comment-13841989
] 

Ming Ma commented on HADOOP-10106:
----------------------------------

Thanks, Sanjay. Moving doRead from Listener class to Reader class is another way to fix the
specific issue found. When I was about to revert doRead, I feel like semantically wise it
is better to have doRead be a member of Reader. So I includes it as part of the fix. What
is the reason to keep doRead method under Listener class?

> 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
>            Priority: Minor
>         Attachments: hadoop_10106_trunk.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#6144)

Mime
View raw message