rocketmq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wlliqip...@apache.org
Subject [rocketmq] branch develop updated: Update Design_Store.md
Date Mon, 11 Mar 2019 11:14:00 GMT
This is an automated email from the ASF dual-hosted git repository.

wlliqipeng pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git


The following commit(s) were added to refs/heads/develop by this push:
     new 0d8c0ba  Update Design_Store.md
     new cdacb29  Merge pull request #1071 from RickySongyz/develop
0d8c0ba is described below

commit 0d8c0ba29f91fe53870e95cb247904587e6dedfa
Author: RickySong <761041702@qq.com>
AuthorDate: Sun Mar 10 12:44:50 2019 +0800

    Update Design_Store.md
---
 docs/en/Design_Store.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/Design_Store.md b/docs/en/Design_Store.md
index d0d1c90..cbc6613 100644
--- a/docs/en/Design_Store.md
+++ b/docs/en/Design_Store.md
@@ -15,7 +15,7 @@ The message storage architecture diagram consists of 3 files related to
message
 
 
 * `CommitLog`:The `CommitLog` file stores message body and metadata sent by producer, and
the message content is not fixed length. The default size of one `CommitLog` file is 1G, the
length of the file name is 20 digits, the left side is zero padded, and the remaining is the
starting offset. For example, `00000000000000000000` represents the first file, the starting
offset is 0, and the file size is 1G=1073741824, when the first `CommitLog` file is full,
the second `CommitLog` file is `0 [...]
-* `ConsumeQueue`: The `ConsumeQueue` is used to improve the performance of message consumption.
Since RocketMQ uses topic-based subscription mode, message consumption is specific to the
topic. Traversing the commitlog file to retrieve messages of one topic is very inefficient.
The consumer can find the messages to be consumed according to the `ConsumeQueue`. The `ConsumeQueue`(logic
consume queue) as an index of the consuming message stores the starting physical offset `offset`
in `Commi [...]
+* `ConsumeQueue`: The `ConsumeQueue` is used to improve the performance of message consumption.
Since RocketMQ uses topic-based subscription mode, message consumption is specific to the
topic. Traversing the commitlog file to retrieve messages of one topic is very inefficient.
The consumer can find the messages to be consumed according to the `ConsumeQueue`. The `ConsumeQueue`(logic
consume queue) as an index of the consuming message stores the starting physical offset `offset`
in `Commi [...]
 * `IndexFile`: The `IndexFile` provides a way to query messages by key or time interval.
The path of the `IndexFile` is `$HOME/store/index/${fileName}`, the file name `fileName` is
named after the timestamp when it was created. One IndexFile's size is about 400M, and it
can store 2000W indexes. The underlying storage of `IndexFile` is designed to implement the
`HashMap` structure in the file system, so RocketMQ's index file is a hash index.
 
 


Mime
View raw message