[rocketmq] branch develop updated: update Design_loadBlancing.md

[wl...@apache.org]

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 8a585ce  update Design_loadBlancing.md
     new 5456e77  Merge pull request #988 from LvChenhui/develop
8a585ce is described below

commit 8a585ced86a9725f5a8b20cbf4b08d2fe820c9e0
Author: Miracles520 <10...@qq.com>
AuthorDate: Sun Mar 3 12:54:57 2019 +0800

    update Design_loadBlancing.md
---
 docs/en/Design_LoadBlancing.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/en/Design_LoadBlancing.md b/docs/en/Design_LoadBlancing.md
index b93b6ea..e6bb66f 100644
--- a/docs/en/Design_LoadBlancing.md
+++ b/docs/en/Design_LoadBlancing.md
@@ -1,11 +1,11 @@
-## 4 Load Balancing
+## Load Balancing
 Load balancing in RocketMQ is accomplished on Client side. Specifically, it can be divided into load balancing at Producer side when sending messages and load balancing at Constumer side when subscribing messages.
 
-### 4.1 Producer Load Balancing
+### 1 Producer Load Balancing
 When the Producer sends a message, it will first find the specified TopicPublishInfo according to Topic. After getting the routing information of TopicPublishInfo, the RocketMQ client will select a queue (MessageQueue) from the messageQueue List in TopicPublishInfo  to send the message by default.Specific fault-tolerant strategies are defined in the MQFaultStrategy class.
 Here is a sendLatencyFaultEnable switch variable, which, if turned on, filters out the Broker agent of not available on the basis of randomly gradually increasing modular arithmetic selection. The so-called "latencyFault Tolerance" refers to a certain period of time to avoid previous failures. For example, if the latency of the last request exceeds 550 Lms, it will evade 3000 Lms; if it exceeds 1000L, it will evade 60000 L; if it is closed, it will choose a queue (MessageQueue) to send m [...]
 
-### 4.2 Consumer Load Balancing
+### 2 Consumer Load Balancing
 In RocketMQ, the two consumption modes (Push/Pull) on the Consumer side are both based on the pull mode to get the message, while in the Push mode it is only a kind of encapsulation of the pull mode, which is essentially implemented as the message pulling thread after pulling a batch of messages from the server. After submitting to the message consuming thread pool, it continues to try again to pull the message to the server. If the message is not pulled, the pull is delayed and continue [...]
 
  1， Heartbeat Packet Sending on Consumer side