[
https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442253#comment-13442253
]
Prashanth Menon edited comment on KAFKA-376 at 8/27/12 1:51 PM:
----------------------------------------------------------------
Here we go, I've attached v3 of the patch. It's effectively the same, but with
some adjustments to compile against latest trunk. Let me know what you guys
think.
Minor edit, thanks for taking care of the other JIRA's. The last few weeks
have been fairly busy, but the good news is that I see a break which I hope to
use to get back into the swing of things :) As for the offsets API, can we
take care of that in a separate JIRA?
was (Author: prashanth.menon):
Here we go, I've attached v3 of the patch. It's effectively the same, but
with some adjustments to compile against latest trunk. Let me know what you
guys think.
> expose different data to fetch requests from the follower replicas and
> consumer clients
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-376
> URL: https://issues.apache.org/jira/browse/KAFKA-376
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Prashanth Menon
> Labels: bugs
> Attachments: KAFKA-376-DRAFT.patch, KAFKA-376-v1.patch,
> KAFKA-376-v2.patch, KAFKA-376-v3.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Currently, the broker always uses highwatermark to calculate the available
> bytes to a fetch request, no matter where the request is from. Instead, we
> should use highwatermark for requests coming from real consumer clients and
> use logendoffset for requests coming from follower replicas.
--
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
