[kafka-site] branch asf-site updated: Update 31 doc folder corresponding to 3.1.0-rc1

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dajac 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 5b7b15b  Update 31 doc folder corresponding to 3.1.0-rc1
5b7b15b is described below

commit 5b7b15b84fa73fd131a1fae93ed99227116c1161
Author: David Jacot <dj...@confluent.io>
AuthorDate: Wed Jan 12 11:03:47 2022 +0100

    Update 31 doc folder corresponding to 3.1.0-rc1
---
 31/design.html                    | 2 +-
 31/generated/connect_metrics.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/31/design.html b/31/design.html
index db71b65..8b7bf92 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 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
+    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
     identical to the leader's log&mdash;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
diff --git a/31/generated/connect_metrics.html b/31/generated/connect_metrics.html
index 136bd29..1781f49 100644
--- a/31/generated/connect_metrics.html
+++ b/31/generated/connect_metrics.html
@@ -1,5 +1,5 @@
-[2021-12-23 22:01:46,410] INFO Metrics scheduler closed (org.apache.kafka.common.metrics.Metrics:659)
-[2021-12-23 22:01:46,416] INFO Metrics reporters closed (org.apache.kafka.common.metrics.Metrics:669)
+[2022-01-12 10:04:37,496] INFO Metrics scheduler closed (org.apache.kafka.common.metrics.Metrics:659)
+[2022-01-12 10:04:37,499] INFO Metrics reporters closed (org.apache.kafka.common.metrics.Metrics:669)
 <table class="data-table"><tbody>
 <tr>
 <td colspan=3 class="mbeanName" style="background-color:#ccc; font-weight: bold;">kafka.connect:type=connect-worker-metrics</td></tr>