hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8263) Stringification of IPC calls not useful
Date Mon, 09 Apr 2012 23:41:17 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HADOOP-8263:

    Attachment: hadoop-8263.txt

Simple patch which just adds a toString method. It turns out it's easy to get the protocol
name and method name, but actually getting to the method contents is difficult in this context.
I elected to do the simple patch instead of the larger refactoring necessary to get the full
parameter printed out.
> Stringification of IPC calls not useful
> ---------------------------------------
>                 Key: HADOOP-8263
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8263
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: hadoop-8263.txt
> Since the Protobufification of Hadoop, the log messages on IPC exceptions on the server
side now read like:
> 12/04/09 16:04:06 INFO ipc.Server: IPC Server handler 9 on 8021, call org.apache.hadoop.ipc.ProtobufRpcEngine$RpcRequestWritable@7087e9bf
from error: org.apache.hadoop.ipc.StandbyException: Operation category READ
is not supported in state standby
> The call should instead stringify the method name and the request protobuf (perhaps abbreviated
if it is longer than a few hundred chars)

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


View raw message