kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From guozh...@apache.org
Subject kafka git commit: HOTFIX: add the hyper link for storage
Date Fri, 04 Aug 2017 16:17:00 GMT
Repository: kafka
Updated Branches:
  refs/heads/trunk c1690da07 -> 5704d8f05

HOTFIX: add the hyper link for storage

Author: Guozhang Wang <wangguoz@gmail.com>

Reviewers: Damian Guy <damian.guy@gmail.com>

Closes #3617 from guozhangwang/KHotfix-introduction-hyperlink

Project: http://git-wip-us.apache.org/repos/asf/kafka/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/5704d8f0
Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/5704d8f0
Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/5704d8f0

Branch: refs/heads/trunk
Commit: 5704d8f05f0d271b62d0170ba5a8fbfceacb4304
Parents: c1690da
Author: Guozhang Wang <wangguoz@gmail.com>
Authored: Fri Aug 4 09:16:57 2017 -0700
Committer: Guozhang Wang <wangguoz@gmail.com>
Committed: Fri Aug 4 09:16:57 2017 -0700

 docs/introduction.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/introduction.html b/docs/introduction.html
index 556aa02..65f021e 100644
--- a/docs/introduction.html
+++ b/docs/introduction.html
@@ -146,7 +146,7 @@
   Kafka does it better. By having a notion of parallelism&mdash;the partition&mdash;within
the topics, Kafka is able to provide both ordering guarantees and load balancing over a pool
of consumer processes. This is achieved by assigning the partitions in the topic to the consumers
in the consumer group so that each partition is consumed by exactly one consumer in the group.
By doing this we ensure that the consumer is the only reader of that partition and consumes
the data in order. Since there are many partitions this still balances the load over many
consumer instances. Note however that there cannot be more consumer instances in a consumer
group than partitions.
-  <h4>Kafka as a Storage System</h4>
+  <h4 id="kafka_storage">Kafka as a Storage System</h4>
   Any message queue that allows publishing messages decoupled from consuming them is effectively
acting as a storage system for the in-flight messages. What is different about Kafka is that
it is a very good storage system.
@@ -160,6 +160,9 @@
   As a result of taking storage seriously and allowing the clients to control their read
position, you can think of Kafka as a kind of special purpose distributed filesystem dedicated
to high-performance, low-latency commit log storage, replication, and propagation.
+  <p>
+  For details about the Kafka's commit log storage and replication design, please read <a
href="https://kafka.apache.org/documentation/#design">this</a> page.
+  </p>
   <h4>Kafka for Stream Processing</h4>
   It isn't enough to just read, write, and store streams of data, the purpose is to enable
real-time processing of streams.

View raw message