This is an automated email from the ASF dual-hosted git repository.
mimaison pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 4c1c868 KAFKA-13374: Update doc to mention read from leader/followers
(#391)
4c1c868 is described below
commit 4c1c868c59df0dbdae169b4bdc9f527592c96615
Author: Luke Chen <[email protected]>
AuthorDate: Mon Jan 3 22:41:57 2022 +0800
KAFKA-13374: Update doc to mention read from leader/followers (#391)
Reviewers: Mickael Maison <[email protected]>
---
31/design.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/31/design.html b/31/design.html
index 8b7bf92..db71b65 100644
--- a/31/design.html
+++ b/31/design.html
@@ -313,7 +313,7 @@
replication factor is one.
<p>
The unit of replication is the topic partition. Under non-failure
conditions, each partition in Kafka has a single leader and zero or more
followers. The total number of replicas including the leader constitute the
- replication factor. All reads and writes go to the leader of the
partition. Typically, there are many more partitions than brokers and the
leaders are evenly distributed among brokers. The logs on the followers are
+ replication factor. All writes go to the leader of the partition, and
reads can go to the leader or the followers of the partition. Typically, there
are many more partitions than brokers and the leaders are evenly distributed
among brokers. The logs on the followers are
identical to the leader's log—all have the same offsets and messages
in the same order (though, of course, at any given time the leader may have a
few as-yet unreplicated messages at the end of its log).
<p>
Followers consume messages from the leader just as a normal Kafka consumer
would and apply them to their own log. Having the followers pull from the
leader has the nice property of allowing the follower to naturally
