hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11058) call_id seems never present in response
Date Mon, 28 Apr 2014 19:50:21 GMT

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

stack commented on HBASE-11058:
-------------------------------

[~charlenehelios] We seem to set the call id on the response here: http://hbase.apache.org/xref/org/apache/hadoop/hbase/ipc/RpcServer.html#360
 If I set DEBUG level on the package org.apache.hadoop.hbase on the client side and run a
client, I see stuff like this:

2014-04-28 12:49:03,753 DEBUG [IPC Client (632537781) connection to c2021.halxg.cloudera.com/10.20.84.27:16020
from stack] ipc.RpcClient: IPC Client (632537781) connection to c2021.halxg.cloudera.com/10.20.84.27:16020
from stack: got response header call_id: 48292, totalSize: 1065 bytes

... which would seem to indicate the server is setting the call_id (I've not looked w/ wireshark).



> call_id seems never present in response
> ---------------------------------------
>
>                 Key: HBASE-11058
>                 URL: https://issues.apache.org/jira/browse/HBASE-11058
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Charlene Sun
>
> version used: 0.98.1
> call_id seems never present in response, could someone take a look and help?
>  
> message ResponseHeader {
>   optional uint32 call_id = 1;
> message RequestHeader {
>   // Monotonically increasing call_id to keep track of RPC requests and their response
>   optional uint32 call_id = 1;



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message