[
https://issues.apache.org/jira/browse/KAFKA-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9938.
------------------------------------
Resolution: Won't Fix
I am going to close this issue as "won't fix." Since the new `Fetch` protocol
versions allows fetching from followers already, there seems little reason to
add this logic just for older versions. The `ReplicaVerificationTool` will
still work for example. Effectively, the behavior of the debug consumer is the
same as the normal consumer.
> Fix debug consumer read from follower for older protocol versions
> -----------------------------------------------------------------
>
> Key: KAFKA-9938
> URL: https://issues.apache.org/jira/browse/KAFKA-9938
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.5.0, 2.4.1
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> In fetch requests, a sentinel of -2 for the replicaId is treated as a "debug
> consumer" and is allowed to fetch from followers. In KIP-392, we added the
> general ability to read from followers, but we require a newer version of the
> protocol. In the process of this change, we lost the ability for older
> version of the fetch protocol to use the "debug consumer" to read from
> followers. As far as I know the only place this capability is used is in the
> ReplicaVerificationTool. We don't expose this capability from the consumer.
> However, it is still technically a regression and should be fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
