You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Colin B. (JIRA)" <ji...@apache.org> on 2013/05/16 01:41:16 UTC
[jira] [Commented] (KAFKA-856) Correlation id for OffsetFetch
request (#2) always responds with 0
[ https://issues.apache.org/jira/browse/KAFKA-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659031#comment-13659031 ]
Colin B. commented on KAFKA-856:
--------------------------------
This would be nice to have in a 0.8 release, so client writers would not have to special case offsetrequest / offsetresponse not maintaining the correlationid. If this will not make it into 0.8, the protocol doc should be updated to reflect this oddity.
> Correlation id for OffsetFetch request (#2) always responds with 0
> ------------------------------------------------------------------
>
> Key: KAFKA-856
> URL: https://issues.apache.org/jira/browse/KAFKA-856
> Project: Kafka
> Issue Type: Bug
> Components: network
> Affects Versions: 0.8, 0.8.1
> Environment: Linux & Mac
> Reporter: Milosz Tanski
> Assignee: Jun Rao
> Attachments: KAFKA-856.patch
>
>
> The in the new Kafka when making an OffsetFetch request the correlation id always response is always sent as 0. It doesn't matter if the client request specifies a correlation id other then 0.
> Example wireshark capture:
> 00000000 00 00 00 31 00 07 00 00 00 00 00 2a 00 03 66 6f ...1.... ...*..fo
> 00000010 6f 00 0a 74 65 73 74 2d 67 72 6f 75 70 00 00 00 o..test- group...
> 00000020 01 00 0a 74 65 73 74 5f 74 6f 70 69 63 00 00 00 ...test_ topic...
> 00000030 01 00 00 00 00 .....
>
> Request #1
> --------
> len: 00 00 00 31
> api: 00 07
> ver: 00 00
> cor: 00 00 00 2a
> cid: 2a 00 03 66 6f 6f
> ....
>
> 00000000 00 00 00 2d 00 00 00 2a 00 03 66 6f 6f 00 00 00 ...-...* ..foo...
> 00000010 01 00 0a 74 65 73 74 5f 74 6f 70 69 63 00 00 00 ...test_ topic...
> 00000020 01 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 ........ ........
> 00000030 03
>
> Response #1
> --------
> len: 00 00 00 2d
> cor: 00 00 00 2a
> cid: 2a 00 03 66 6f 6f
> ....
>
> 00000035 00 00 00 35 00 02 00 00 00 00 00 2a 00 03 66 6f ...5.... ...*..fo
> 00000045 6f ff ff ff ff 00 00 00 01 00 0a 74 65 73 74 5f o....... ...test_
> 00000055 74 6f 70 69 63 00 00 00 01 00 00 00 00 ff ff ff topic... ........
> 00000065 ff ff ff ff fe 00 00 00 01 ........ .
>
> Request #2
> ---------
> len: 00 00 00 35
> api: 00 02
> ver: 00 00
> cor: 00 00 00 2a
> cid: 00 03 66 6f 6f
>
> 00000031 00 00 00 2a 00 00 00 00 00 00 00 01 00 0a 74 65 ...*.... ......te
> 00000041 73 74 5f 74 6f 70 69 63 00 00 00 01 00 00 00 00 st_topic ........
> 00000051 00 00 00 00 00 01 00 00 00 00 00 00 00 00 ........ ......
>
> Response #2:
> ----------
> len: 00 00 00 2a
> cor: 00 00 00 00
> alen: 00 00 00 01
> ....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira