[
https://issues.apache.org/jira/browse/HBASE-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983903#comment-13983903
]
Charlene Sun commented on HBASE-11058:
--------------------------------------
Yes. I see the code is setting the call_id. It is strange why I am not getting
the call_id in the response packet.
For example,
test case
hbase(main):060:0> scan 't2',{COLUMNS=>['c1','c2'],STARTROW=>'This'}
00000000 : 0b 08 f7 01 1a 04 53 63 61 6e 20 01 61 0a 37 08 ......Scan .a.7.
00000010 : 01 12 33 74 32 2c 2c 31 33 39 38 30 30 37 39 30 ..3t2,,139800790
00000020 : 33 39 33 38 2e 30 31 30 33 65 61 33 65 31 65 61 3938.0103ea3e1ea
00000030 : 34 30 63 31 66 63 30 61 65 37 63 65 34 34 33 65 40c1fc0ae7ce443e
00000040 : 32 38 35 64 30 2e 12 22 0a 04 0a 02 63 31 0a 04 285d0.."....c1..
00000050 : 0a 02 63 32 12 0a 0a 05 5f 72 61 77 5f 12 01 00 ..c2...._raw_...
00000060 : 1a 04 54 68 69 73 38 01 40 01 20 00 28 00 ..This8.@. .(.
following is its response packet
00000000 : 00 00 00 15 b0 8b be c1 a3 98 72 18 00 18 01 20 ..........r....
00000010 : e0 d4 03 10 e4 b2 b0 8b 89 .........
I should be getting 0x f701 call_id in response packet.
Please advise.
Charlene Sun
> 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)
