diff --git a/docs/cn/Configuration_TLS.md b/docs/cn/Configuration_TLS.md index fe83710db90..ff7fbfd162c 100644 --- a/docs/cn/Configuration_TLS.md +++ b/docs/cn/Configuration_TLS.md @@ -83,13 +83,13 @@ tls.client.trustCertPath=/opt/certFiles/ca.pem ### 3.1 编辑runserver.sh，在JAVA_OPT中增加以下内容： ```shell -JAVA_OPT="${JAVA_OPT} -Dtls.server.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties" +JAVA_OPT="${JAVA_OPT} -Dtls.server.mode=enforcing -Dtls.config.file=/opt/rocketmq-5.5.0/conf/tls.properties" ``` ### 3.2 编辑runbroker.sh，在JAVA_OPT中增加以下内容： ```shell -JAVA_OPT="${JAVA_OPT} -Dorg.apache.rocketmq.remoting.ssl.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties -Dtls.enable=true" +JAVA_OPT="${JAVA_OPT} -Dorg.apache.rocketmq.remoting.ssl.mode=enforcing -Dtls.config.file=/opt/rocketmq-5.5.0/conf/tls.properties -Dtls.enable=true" ``` # 4 客户端连接 diff --git a/docs/cn/Example_Simple_cn.md b/docs/cn/Example_Simple_cn.md index f0a2b6a1dea..9c8729223bb 100644 --- a/docs/cn/Example_Simple_cn.md +++ b/docs/cn/Example_Simple_cn.md @@ -9,12 +9,12 @@ maven: org.apache.rocketmq rocketmq-client - 4.3.0 + 5.5.0 ``` gradle: ``` java -compile 'org.apache.rocketmq:rocketmq-client:4.3.0' +compile 'org.apache.rocketmq:rocketmq-client:5.5.0' ``` ### 2 发送消息 ##### 2.1 使用Producer发送同步消息 diff --git a/docs/cn/RocketMQ_Example.md b/docs/cn/RocketMQ_Example.md index 77c1bd7b270..12f637cad34 100644 --- a/docs/cn/RocketMQ_Example.md +++ b/docs/cn/RocketMQ_Example.md @@ -54,12 +54,12 @@ org.apache.rocketmq rocketmq-client - 4.9.1 + 5.5.0 ``` `gradle` ``` -compile 'org.apache.rocketmq:rocketmq-client:4.3.0' +compile 'org.apache.rocketmq:rocketmq-client:5.5.0' ``` ### 1.2 消息发送 diff --git a/docs/en/Configuration_TLS.md b/docs/en/Configuration_TLS.md index 54a63f4ab15..faea26766dd 100644 --- a/docs/en/Configuration_TLS.md +++ b/docs/en/Configuration_TLS.md @@ -78,14 +78,14 @@ The value of "tls.config.file" needs to be replaced by the file path created in ### 3.1 Edit runserver.sh Add following content in JAVA_OPT: ```shell -JAVA_OPT="${JAVA_OPT} -Dtls.server.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties" +JAVA_OPT="${JAVA_OPT} -Dtls.server.mode=enforcing -Dtls.config.file=/opt/rocketmq-5.5.0/conf/tls.properties" ``` ### 3.2 Edit runbroker.sh Add following content in JAVA_OPT: ```shell -JAVA_OPT="${JAVA_OPT} -Dorg.apache.rocketmq.remoting.ssl.mode=enforcing -Dtls.config.file=/opt/rocketmq-4.9.3/conf/tls.properties -Dtls.enable=true" +JAVA_OPT="${JAVA_OPT} -Dorg.apache.rocketmq.remoting.ssl.mode=enforcing -Dtls.config.file=/opt/rocketmq-5.5.0/conf/tls.properties -Dtls.enable=true" ``` # 4 Client connection diff --git a/docs/en/Design_LoadBlancing.md b/docs/en/Design_LoadBalancing.md similarity index 98% rename from docs/en/Design_LoadBlancing.md rename to docs/en/Design_LoadBalancing.md index 05c178464dc..f3547f98de2 100644 --- a/docs/en/Design_LoadBlancing.md +++ b/docs/en/Design_LoadBalancing.md @@ -2,7 +2,7 @@ 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 Consumer side when subscribing messages. ### 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. +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 agents that are 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 30000 Lms; if it exceeds 1000L, it will evade 60000L; if it is closed, it will choose a queue (MessageQueue) to send messages by randomly gradually increasing modular arithmetic, and the latencyFault Tolerance mechanism is the key to achieve high availability of message sending. ### Consumer Load Balancing diff --git a/docs/en/Design_Trancation.md b/docs/en/Design_Transaction.md similarity index 97% rename from docs/en/Design_Trancation.md rename to docs/en/Design_Transaction.md index 287378e37a6..1563d528286 100644 --- a/docs/en/Design_Trancation.md +++ b/docs/en/Design_Transaction.md @@ -1,6 +1,6 @@ # Transaction Message ## 1 Transaction Message -Apache RocketMQ supports distributed transaction message from version 4.3.0. RocketMQ implements transaction message by using the protocol of 2PC(two-phase commit), in addition adding a compensation logic to handle timeout-case or failure-case of commit-phase, as shown below. +Apache RocketMQ supports distributed transaction message from version 4.3.0. RocketMQ implements transaction message by using the protocol of 2PC(two-phase commit), in addition to adding a compensation logic to handle timeout-case or failure-case of commit-phase, as shown below. ![](../cn/image/rocketmq_design_10.png) diff --git a/docs/en/Example_Simple.md b/docs/en/Example_Simple.md index 0ce4924cc78..8f759065840 100644 --- a/docs/en/Example_Simple.md +++ b/docs/en/Example_Simple.md @@ -9,12 +9,12 @@ maven: org.apache.rocketmq rocketmq-client - 4.3.0 + 5.5.0 ``` gradle: ``` java -compile 'org.apache.rocketmq:rocketmq-client:4.3.0' +compile 'org.apache.rocketmq:rocketmq-client:5.5.0' ``` ### 2 Send Messages ##### 2.1 Use Producer to Send Synchronous Messages diff --git a/docs/en/Operations_Trace.md b/docs/en/Operations_Trace.md index 74c2cde1af2..28d8cec95b7 100644 --- a/docs/en/Operations_Trace.md +++ b/docs/en/Operations_Trace.md @@ -11,7 +11,7 @@ ## 2 Support for Message Trace Cluster Deployment -### 2.1 Broker Configuration Fille +### 2.1 Broker Configuration File The properties profile content of the Broker side enabled message trace feature is pasted here: diff --git a/docs/en/Troubleshoopting.md b/docs/en/Troubleshooting.md similarity index 100% rename from docs/en/Troubleshoopting.md rename to docs/en/Troubleshooting.md diff --git a/docs/en/design.md b/docs/en/design.md index c919862b7bc..0e671a181b0 100644 --- a/docs/en/design.md +++ b/docs/en/design.md @@ -52,7 +52,7 @@ ### 5 Transactional Message -Apache RocketMQ supports distributed transactional message from version 4.3.0. RocketMQ implements transactional message by using the protocol of 2PC(two-phase commit), in addition adding a compensation logic to handle timeout-case or failure-case of commit-phase, as shown below. +Apache RocketMQ supports distributed transactional message from version 4.3.0. RocketMQ implements transactional message by using the protocol of 2PC(two-phase commit), in addition to adding a compensation logic to handle timeout-case or failure-case of commit-phase, as shown below. ![](../cn/image/rocketmq_design_10.png)