This is an automated email from the ASF dual-hosted git repository.
huzongtang 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 2758825 [RIP-9]Modify Design_Remoting.md
2758825 is described below
commit 275882577b965e715e4371f7af50489440a08e39
Author: Yalong Li <[email protected]>
AuthorDate: Thu Mar 7 15:50:13 2019 +0800
[RIP-9]Modify Design_Remoting.md
---
docs/en/Design_Remoting.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/en/Design_Remoting.md b/docs/en/Design_Remoting.md
index ff2c99d..b90413e 100644
--- a/docs/en/Design_Remoting.md
+++ b/docs/en/Design_Remoting.md
@@ -1,7 +1,7 @@
## 2 Communication Mechanism
RocketMQ message queue cluster mainly includes four roles: NameServer, Broker
(Master/Slave), Producer and Consumer. The basic communication process is as
follows:
(1) After Broker start-up, it needs to complete one operation: register itself
to NameServer, and then report Topic routing information to NameServer at
regular intervals of 30 seconds.
-(2) When message producer Producer sends a message as a client, it needs to
obtain routing information from the local cache TopicPublishInfoTable according
to the Topic of the message. If not, it will be retrieved from NameServer and
update to local cache, at the same time, Producer will retrieve routing
information from NameServer every 30 seconds by default.
+(2) When message Producer sends a message as a client, it needs to obtain
routing information from the local cache TopicPublishInfoTable according to the
Topic of the message. If not, it will be retrieved from NameServer and update
to local cache, at the same time, Producer will retrieve routing information
from NameServer every 30 seconds by default.
(3) Message producer Producer chooses a queue to send the message according to
the routing information obtained in 2); Broker receives the message and records
it in disk as the receiver of the message.
(4) After message consumer Consumer get the routing information according to
2) and complete the load balancing of the client, then select one or several
message queues to pull messages and consume them.
