[
https://issues.apache.org/jira/browse/KAFKA-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429682#comment-17429682
]
Jacek Laskowski commented on KAFKA-13374:
-----------------------------------------
Correct. Found this in [What's New in Apache Kafka
2.4|https://blogs.apache.org/kafka/entry/what-s-new-in-apache1]:
bq. KIP-392: Allow consumers to fetch from closest replica
bq.
bq. Historically, consumers were only allowed to fetch from leaders. In
multi-datacenter deployments, this often means that consumers are forced to
incur expensive cross-datacenter network costs in order to fetch from the
leader. With KIP-392, Kafka now supports reading from follower replicas. This
gives the broker the ability to redirect consumers to nearby replicas in order
to save costs.
bq.
bq. See KIP-392 and this blog post for more details.
It'd be nice to have it in the official docs (so I'll remember it when using
the docs during Kafka workshops :)).
> [Docs] - All reads from the leader of the partition even after KIP-392?
> -----------------------------------------------------------------------
>
> Key: KAFKA-13374
> URL: https://issues.apache.org/jira/browse/KAFKA-13374
> Project: Kafka
> Issue Type: Bug
> Reporter: Robin Moffatt
> Priority: Trivial
>
> On `https://kafka.apache.org/documentation/#design_replicatedlog` it says
> > All reads and writes go to the leader of the partition.
> However with KIP-392 I didn't think this was the case any more. If so, the
> doc should be updated to clarify.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
