This is an automated email from the ASF dual-hosted git repository.
dinglei pushed a commit to branch new-official-website
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/new-official-website by this
push:
new 0987901d fix build error for en version of new website (#187)
0987901d is described below
commit 0987901d12330ea17662af82cc7ea807b560cb9f
Author: dinglei <[email protected]>
AuthorDate: Sat Aug 20 23:25:05 2022 +0800
fix build error for en version of new website (#187)
---
.../current/01-\344\273\213\347\273\215/03whatis.md" | 6 +++---
.../current/02-\347\224\237\344\272\247\350\200\205/05message1.md" | 6 +++---
.../current/02-\347\224\237\344\272\247\350\200\205/06message2.md" | 2 +-
.../current/02-\347\224\237\344\272\247\350\200\205/08message4.md" | 2 +-
.../current/02-\347\224\237\344\272\247\350\200\205/09message5.md" | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/01-\344\273\213\347\273\215/03whatis.md"
"b/i18n/en/docusaurus-plugin-content-docs/current/01-\344\273\213\347\273\215/03whatis.md"
index b4163fe3..dbf58fe4 100644
---
"a/i18n/en/docusaurus-plugin-content-docs/current/01-\344\273\213\347\273\215/03whatis.md"
+++
"b/i18n/en/docusaurus-plugin-content-docs/current/01-\344\273\213\347\273\215/03whatis.md"
@@ -38,7 +38,7 @@ learn more ➡️ [basic concept](/docs/生产者/04concept1)
## RocketMQ's message model, a simple Pub/Sub model
-
+
@@ -59,7 +59,7 @@ In a **topic-based** system, messages are published on topics
or channels.Consum
-
+
@@ -85,7 +85,7 @@ The **Broker** that stores message topics is the proxy server
for the actual dep
How do Producer and Consumer find the addresses of Topic and Broker? How are
messages sent and received?
-
+
The main Apache RocketMQ components are Producers, Consumers, NameServers, and
Brokers:
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/05message1.md"
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/05message1.md"
index e5dd6f93..0551a949 100644
---
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/05message1.md"
+++
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/05message1.md"
@@ -50,7 +50,7 @@ Apache RocketMQ sends messages in three ways: **synchronous,
asynchronous, and o
Synchronous Sending is a communication method in which the message sender
sends a message and will send the next message only after receiving a
synchronous response from the server. Reliable synchronous transmission is
widely used in various scenarios, such as important notification messages,
short message notifications, etc.
-
+
The entire code for synchronous sending is as follows:
1. **Create a Producer**. Create a DefaultMQProducer in advance. The Producer
should contain the name of the Producer group, which is a collection of
Producer, they would send the same type of messages with identical logic.
@@ -87,7 +87,7 @@ public class SyncProducer {
### 3.2 Asynchronous Sending
-
+
Asynchronous sending is a sending method in which the sender sends messages
continuously without waiting for the server to return a response.
@@ -141,7 +141,7 @@ The only difference between asynchronous and synchronous
sending methods is the
### 3.3 One-Way Sending
-
+
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/06message2.md"
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/06message2.md"
index 41e7f8eb..fe9f88a3 100644
---
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/06message2.md"
+++
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/06message2.md"
@@ -4,7 +4,7 @@
Ordered messages have strict requirements on the order in which they are sent
and consumed.
For a given Topic, messages are published and consumed strictly on a
first-in-first-out (FIFO) basis, i.e., messages published first will be
consumed first. Furthermore, as shown in the following figure, partitioned
ordered messages are supported in Apache RocketMQ. The messages can be
partitioned according to a certain criterion (e.g., ShardingKey). Messages with
the same ShardingKey are assigned to the identical queue and consumed in order.
-
+
Ordered messages are also used in a wide range of application scenarios, such
as the example of creating orders, the same order generation, payment, and
shipment should be executed sequentially. In the case of simple messages, the
messages of Order A may be polled and sent to different queues. The messages of
different queues will not be able to maintain order. In contrast, ordered
messages are sent by routing the sequence of messages with the same ShardingKey
(same order number) to a lo [...]
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/08message4.md"
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/08message4.md"
index 1a3e4d3f..deb29629 100644
---
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/08message4.md"
+++
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/08message4.md"
@@ -2,7 +2,7 @@
In the case of certain requirements on throughput, Apache RocketMQ can send
messages after grouping them into batches. The approach is able to increase
throughput and decrease the times of API and network calls.
-
+
```javascript {10,11,12,13}
public class SimpleBatchProducer {
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/09message5.md"
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/09message5.md"
index 5d8e92fa..fdb378f3 100644
---
"a/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/09message5.md"
+++
"b/i18n/en/docusaurus-plugin-content-docs/current/02-\347\224\237\344\272\247\350\200\205/09message5.md"
@@ -4,7 +4,7 @@
In some scenarios where there is a strong need for data consistency, Apache
RocketMQ transactional messages can be used to ensure consistency of upstream
and downstream data.
-
+
Transactional messages are send in two phases. At first, a half message will
be delivered, which refers to a message is successfully sent to the MQ server,
but the server did not receive the second acknowledgement of the message from
the Producer, then the message will be marked as “temporarily undeliverable”
state.
@@ -14,7 +14,7 @@ If the second acknowledgement of a transactional message is
lost due to network
The detailed execute flow of the transactional message is shown in the
following diagram:
-
+
## Transactional Message Sending Procedure
