[
https://issues.apache.org/jira/browse/HBASE-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983968#comment-13983968
]
stack commented on HBASE-11058:
-------------------------------
I took a quick look w/ wire shark and seem to be able to match up a few
requests and responses via their call_id.
Below is an isMasterRunning
00:00:00:17:15:08:02:1a:0f:49:73:4d:61:73:74:65:72:52:75:6e:6e:69:6e:67:20:01:00
00:00:00:06:02:08:02:02:08:01
See how the id matches request/response 08:02.
This is the next call... getTableNames:
00:00:00:15:13:08:03:1a:0d:47:65:74:54:61:62:6c:65:4e:61:6d:65:73:20:01:00
00:00:00:1a:02:08:03:16:0a:14:0a:07:64:65:66:61:75:6c:74:12:09:54:65:73:74:54:61:62:6c:65
08:03
Here is a scan meta:
00:00:00:12:0a:08:0c:1a:04:53:63:61:6e:20:01:06:18:1c:20:00:28:01
00:00:00:08:02:08:0c:04:10:1c:18:00
08:0c
08 is the field number #1 right shifted by 3 and the type is 0 (uint3). The
value is 0xc, a varint:
https://developers.google.com/protocol-buffers/docs/encoding
Could you be matching the wrong response?
> 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)
