[jira] [Commented] (KAFKA-376) expose different data to fetch requests from the follower replicas and consumer clients

["Prashanth Menon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426249#comment-13426249 ] 

Prashanth Menon commented on KAFKA-376:
---------------------------------------

Thanks for the comments, Jun.

1. Do we currently support this?  The fetch requests always check that the leader is on the broker handling the request before actually reading from the log, so I'm not sure how a read on a follower succeeds?

2.1, 2.2, 2.3, 2.4, 2.5 All valid.  Will upload new patch later this week.

I assume you mean, KAFKA-343?  I've been following it, and yes, it's grown quite large/complex hahaha.  I'll definitely wait for that to get ironed out and committed.
                
> 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
>         Attachments: KAFKA-376-DRAFT.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira