[
https://issues.apache.org/jira/browse/KAFKA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Palino updated KAFKA-1588:
-------------------------------
Description:
When performing an OffsetRequest, if you request the same topic and partition
combination in a single request more than once (for example, if you want to get
both the head and tail offsets for a partition in the same request), you will
get a response for both, but they will be the same offset.
We identified that the problem is that when the offset response is assembled, a
map is used to store the offset info before it is converted to the response
format and sent to the client. Therefore, the second request for a
topic/partition combination will overwrite the offset from the first request.
was:
When performing an OffsetFetchRequest, if you request the same topic and
partition combination in a single request more than once (for example, if you
want to get both the head and tail offsets for a partition in the same
request), you will get a response for both, but they will be the same offset.
We identified that the problem is that when the offset response is assembled, a
map is used to store the offset info before it is converted to the response
format and sent to the client. Therefore, the second request for a
topic/partition combination will overwrite the offset from the first request.
Thanks, Jun, I had written that incorrectly. It is the OffsetRequest that
manifests the problem. I've edited the description.
> Offset response does not support two requests for the same topic/partition
> combo
> --------------------------------------------------------------------------------
>
> Key: KAFKA-1588
> URL: https://issues.apache.org/jira/browse/KAFKA-1588
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2
> Reporter: Todd Palino
>
> When performing an OffsetRequest, if you request the same topic and partition
> combination in a single request more than once (for example, if you want to
> get both the head and tail offsets for a partition in the same request), you
> will get a response for both, but they will be the same offset.
> We identified that the problem is that when the offset response is assembled,
> a map is used to store the offset info before it is converted to the response
> format and sent to the client. Therefore, the second request for a
> topic/partition combination will overwrite the offset from the first request.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
