This is an automated email from the ASF dual-hosted git repository.
jinrongtong 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 5e876769b Modify img links (#523)
5e876769b is described below
commit 5e876769b70ded647dae57e56a235a15350591ff
Author: Jack Tsai <[email protected]>
AuthorDate: Fri Mar 3 22:46:25 2023 +0800
Modify img links (#523)
Co-authored-by: tsaitsung-han.tht <[email protected]>
---
docs/04-deployment/04Exporter.md | 7 +++----
docs/05-bestPractice/07subscribe.md | 10 +++++-----
...205\263\347\263\273\344\270\200\350\207\264-1.jpeg" | Bin 0 -> 31548 bytes
...205\263\347\263\273\344\270\200\350\207\264-2.jpeg" | Bin 0 -> 49141 bytes
...205\263\347\263\273\344\270\200\350\207\264-3.jpeg" | Bin 0 -> 50012 bytes
...205\263\347\263\273\344\270\200\350\207\264-4.jpeg" | Bin 0 -> 46018 bytes
...205\263\347\263\273\344\270\200\350\207\264-5.jpeg" | Bin 0 -> 47032 bytes
docs/picture/RocketMQ Prometheus Exporter - 2.jpeg | Bin 0 -> 92834 bytes
docs/picture/RocketMQ Prometheus Exporter-1.jpeg | Bin 0 -> 94414 bytes
docs/picture/RocketMQ Prometheus Exporter-3.jpeg | Bin 0 -> 140264 bytes
.../current/04-deployment/04Exporter.md | 6 +++---
.../current/05-bestPractice/07subscribe.md | 10 +++++-----
...205\263\347\263\273\344\270\200\350\207\264-1.jpeg" | Bin 0 -> 31548 bytes
...205\263\347\263\273\344\270\200\350\207\264-2.jpeg" | Bin 0 -> 49141 bytes
...205\263\347\263\273\344\270\200\350\207\264-3.jpeg" | Bin 0 -> 50012 bytes
...205\263\347\263\273\344\270\200\350\207\264-4.jpeg" | Bin 0 -> 46018 bytes
...205\263\347\263\273\344\270\200\350\207\264-5.jpeg" | Bin 0 -> 47032 bytes
.../picture/RocketMQ Prometheus Exporter - 2.jpeg | Bin 0 -> 92834 bytes
.../picture/RocketMQ Prometheus Exporter-1.jpeg | Bin 0 -> 94414 bytes
.../picture/RocketMQ Prometheus Exporter-3.jpeg | Bin 0 -> 140264 bytes
.../version-5.0/05-deploymentOperations/05Exporter.md | 6 +++---
.../version-5.0/06-bestPractice/05subscribe.md | 6 +++---
...205\263\347\263\273\344\270\200\350\207\264-1.jpeg" | Bin 0 -> 31548 bytes
...205\263\347\263\273\344\270\200\350\207\264-2.jpeg" | Bin 0 -> 46018 bytes
...205\263\347\263\273\344\270\200\350\207\264-3.jpeg" | Bin 0 -> 47032 bytes
.../picture/RocketMQ Prometheus Exporter - 2.jpeg | Bin 0 -> 92834 bytes
.../picture/RocketMQ Prometheus Exporter-1.jpeg | Bin 0 -> 94414 bytes
.../picture/RocketMQ Prometheus Exporter-3.jpeg | Bin 0 -> 140264 bytes
src/pages/contact.md | 2 +-
src/pages/version 2.md | 14 +++++++-------
src/pages/version.md | 14 +++++++-------
"static/img/5.0\351\200\237\350\247\210-1.jpeg" | Bin 0 -> 28649 bytes
"static/img/5.0\351\200\237\350\247\210-2.jpeg" | Bin 0 -> 79021 bytes
"static/img/5.0\351\200\237\350\247\210-3.jpeg" | Bin 0 -> 75502 bytes
"static/img/5.0\351\200\237\350\247\210-4.jpeg" | Bin 0 -> 24028 bytes
"static/img/5.0\351\200\237\350\247\210-5.jpeg" | Bin 0 -> 73133 bytes
"static/img/5.0\351\200\237\350\247\210-6.jpeg" | Bin 0 -> 47136 bytes
"static/img/5.0\351\200\237\350\247\210-7.jpeg" | Bin 0 -> 132408 bytes
static/img/contact.jpeg | Bin 0 -> 80923 bytes
.../version-5.0/05-deploymentOperations/05Exporter.md | 6 +++---
.../version-5.0/06-bestPractice/05subscribe.md | 6 +++---
...205\263\347\263\273\344\270\200\350\207\264-1.jpeg" | Bin 0 -> 31548 bytes
...205\263\347\263\273\344\270\200\350\207\264-2.jpeg" | Bin 0 -> 46018 bytes
...205\263\347\263\273\344\270\200\350\207\264-3.jpeg" | Bin 0 -> 47032 bytes
.../picture/RocketMQ Prometheus Exporter - 2.jpeg | Bin 0 -> 92834 bytes
.../picture/RocketMQ Prometheus Exporter-1.jpeg | Bin 0 -> 94414 bytes
.../picture/RocketMQ Prometheus Exporter-3.jpeg | Bin 0 -> 140264 bytes
47 files changed, 43 insertions(+), 44 deletions(-)
diff --git a/docs/04-deployment/04Exporter.md b/docs/04-deployment/04Exporter.md
index 403208416..61f59d04f 100644
--- a/docs/04-deployment/04Exporter.md
+++ b/docs/04-deployment/04Exporter.md
@@ -9,7 +9,7 @@
:::
`Rocketmq-expoter` 获取监控指标的流程如下图所示，Expoter 通过 MQAdminExt 向 MQ 集群请求数据，请求到的数据通过
MetricService 规范化成 Prometheus 需要的格式，然后通过 /metics 接口暴露给 Promethus。
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l5ui30u2j21dy0u076k.jpg";></img>
+
@@ -131,7 +131,7 @@ MetricCollectTask 类中有 5 个定时任务，分别为 collectTopicOffset、c
### Rocketmq-exporter 收集指标流程图
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l64nrfwrj20oz0btmze.jpg";></img>
+
## 快速开始
@@ -159,8 +159,7 @@ MetricCollectTask 类中有 5 个定时任务，分别为 collectTopicOffset、c
本地启动默认为: localhost:9090 ,则可对收集到的指标值进行查看,如下图所示:
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l66aaa7tj215y0bzwi0.jpg";></img>
-
+
:::tip
为了达到更好的可视化效果,观察指标值变化趋势, promethus 搭配 grafana 效果更佳哦!
diff --git a/docs/05-bestPractice/07subscribe.md
b/docs/05-bestPractice/07subscribe.md
index c91399e59..e9f39e851 100644
--- a/docs/05-bestPractice/07subscribe.md
+++ b/docs/05-bestPractice/07subscribe.md
@@ -14,7 +14,7 @@
如下图所示，同一Group
ID下的三个Consumer实例C1、C2和C3分别都订阅了TopicA，且订阅TopicA的Tag也都是Tag1，符合订阅关系一致原则。
-
+
@@ -40,7 +40,7 @@ C1、C2、C3的订阅关系一致，即C1、C2、C3订阅消息的代码必须
如下图所示，同一Group
ID下的三个Consumer实例C1、C2和C3分别都订阅了TopicB，订阅TopicB的Tag也都是Tag2和Tag3，表示订阅TopicB中所有Tag为Tag2或Tag3的消息，且顺序一致都是Tag2||Tag3，符合订阅关系一致性原则。
-
+
**正确示例代码二**
@@ -62,7 +62,7 @@ C1、C2、C3的订阅关系一致，即C1、C2、C3订阅消息的代码必须
如下图所示，同一Group
ID下的三个Consumer实例C1、C2和C3分别都订阅了TopicA和TopicB，且订阅的TopicA都未指定Tag，即订阅TopicA中的所有消息，订阅的TopicB的Tag都是Tag2和Tag3，表示订阅TopicB中所有Tag为Tag2或Tag3的消息，且顺序一致都是Tag2||Tag3，符合订阅关系一致原则。
-
+
**正确示例代码三**
@@ -111,7 +111,7 @@ C1、C2、C3的订阅关系一致，即C1、C2、C3订阅消息的代码必须
如下图所示，同一Group
ID下的三个Consumer实例C1、C2和C3分别订阅了TopicA、TopicB和TopicC，订阅的Topic不一致，不符合订阅关系一致性原则。
-
+
**错误示例代码一**
@@ -161,7 +161,7 @@ C1、C2、C3的订阅关系一致，即C1、C2、C3订阅消息的代码必须
如下图所示，同一Group
ID下的三个Consumer实例C1、C2和C3分别都订阅了TopicA，但是C1订阅TopicA的Tag为**Tag1**，C2和C3订阅的TopicA的Tag为**Tag2**，订阅同一Topic的Tag不一致，不符合订阅关系一致性原则。
-
+
**错误示例代码二**
diff --git
"a/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
new file mode 100644
index 000000000..bdf30130b
Binary files /dev/null and
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
differ
diff --git
"a/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
new file mode 100644
index 000000000..8d4da82e0
Binary files /dev/null and
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
differ
diff --git
"a/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
new file mode 100644
index 000000000..44e841efd
Binary files /dev/null and
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
differ
diff --git
"a/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-4.jpeg"
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-4.jpeg"
new file mode 100644
index 000000000..d4fcd2c70
Binary files /dev/null and
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-4.jpeg"
differ
diff --git
"a/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-5.jpeg"
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-5.jpeg"
new file mode 100644
index 000000000..4f2e99226
Binary files /dev/null and
"b/docs/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-5.jpeg"
differ
diff --git a/docs/picture/RocketMQ Prometheus Exporter - 2.jpeg
b/docs/picture/RocketMQ Prometheus Exporter - 2.jpeg
new file mode 100644
index 000000000..8243169b1
Binary files /dev/null and b/docs/picture/RocketMQ Prometheus Exporter - 2.jpeg
differ
diff --git a/docs/picture/RocketMQ Prometheus Exporter-1.jpeg
b/docs/picture/RocketMQ Prometheus Exporter-1.jpeg
new file mode 100644
index 000000000..b894b6db0
Binary files /dev/null and b/docs/picture/RocketMQ Prometheus Exporter-1.jpeg
differ
diff --git a/docs/picture/RocketMQ Prometheus Exporter-3.jpeg
b/docs/picture/RocketMQ Prometheus Exporter-3.jpeg
new file mode 100644
index 000000000..f0f9ac2f1
Binary files /dev/null and b/docs/picture/RocketMQ Prometheus Exporter-3.jpeg
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/04-deployment/04Exporter.md
b/i18n/en/docusaurus-plugin-content-docs/current/04-deployment/04Exporter.md
index 1397517b5..3b884db51 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/04-deployment/04Exporter.md
+++ b/i18n/en/docusaurus-plugin-content-docs/current/04-deployment/04Exporter.md
@@ -8,7 +8,7 @@ In previous versions, there were 87 concurrentHashMaps, but
since the Map does n
:::
The process for `Rocketmq-exporter` to obtain monitoring metrics is shown in
the following figure. The exporter requests data from the MQ cluster through
MQAdminExt, and the requested data is standardized into the format required by
Prometheus through the MetricService, and then exposed to Promethus through the
`/metrics` interface.
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l5ui30u2j21dy0u076k.jpg";></img>
+
### Metric structure
@@ -127,7 +127,7 @@ The MetricCollectTask class has five scheduled tasks:
collectTopicOffset, collec
### Rocketmq-exporter collects metrics flowchart
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l64nrfwrj20oz0btmze.jpg";></img>
+
## Quick star
@@ -155,7 +155,7 @@ Configure Prometheus's static_config: -targets to the
exporter's starting IP and
If the localhost starts at the default localhost:9090, you can view the
collected metric values, as shown in the following figure:
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l66aaa7tj215y0bzwi0.jpg";></img>
+
:::tip
For better visualization effects and to observe the trend of metric value
changes, Prometheus is better used with Grafana!
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/05-bestPractice/07subscribe.md
b/i18n/en/docusaurus-plugin-content-docs/current/05-bestPractice/07subscribe.md
index 65cb48b1b..1e9594d57 100644
---
a/i18n/en/docusaurus-plugin-content-docs/current/05-bestPractice/07subscribe.md
+++
b/i18n/en/docusaurus-plugin-content-docs/current/05-bestPractice/07subscribe.md
@@ -12,7 +12,7 @@ Consistent subscription relationship: all consumer instances
in the same consume
As shown in the following figure, three Consumer instances C1, C2, and C3 in
the same Group ID have all subscribed to TopicA, and the Tag of their
subscription to TopicA is also Tag1, which conforms to the principle of
consistent subscription.
-
+
**Correct example code 1:**
@@ -34,7 +34,7 @@ The subscription relationships of C1, C2, and C3 are
consistent, meaning the cod
As shown in the following figure, the three Consumer instances C1, C2, and C3
in the same Group ID have all subscribed to TopicB and have subscribed to Tag2
and Tag3 for TopicB, which means they have subscribed to all messages in TopicB
with Tag2 or Tag3, and the order is consistent as Tag2||Tag3, meeting the
principle of subscription relationship consistency.
-
+
**Correct example code 2:**
@@ -56,7 +56,7 @@ The subscription relationships of C1, C2, and C3 are
consistent, meaning the cod
As shown in the following figure, the three Consumer instances C1, C2, and C3
in the same Group ID have all subscribed to TopicA and TopicB, and their
subscription to TopicA does not specify any Tag, which means they subscribe to
all messages in TopicA, and their subscription to TopicB's Tag is Tag1 and
Tag2, which means they subscribe to all messages in TopicB with Tag1 or Tag2,
and the order is consistent as Tag1||Tag2, meeting the principle of
subscription relationship consistency.
-
+
**Correct example code 3:**
@@ -105,7 +105,7 @@ You can check the consistency of the subscription
relationship of the specified
As shown in the following figure, the three Consumer instances C1, C2, and C3
in the same Group ID have subscribed to TopicA, TopicB, and TopicC,
respectively, and their subscriptions to the Topics are not the same, which
does not meet the principle of subscription relationship consistency.
-
+
**Error example code 1**
@@ -155,7 +155,7 @@ As shown in the following figure, the three Consumer
instances C1, C2, and C3 in
As shown in the following figure, the three Consumer instances C1, C2, and C3
in the same Group ID have all subscribed to TopicA, but C1 subscribes to Tag1
for TopicA, C2 and C3 subscribe to Tag2 for TopicA, and the subscriptions to
the same Topic's Tag are not the same, which does not meet the principle of
subscription relationship consistency.
-
+
**Error example code 2**
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
new file mode 100644
index 000000000..bdf30130b
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
differ
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
new file mode 100644
index 000000000..8d4da82e0
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
differ
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
new file mode 100644
index 000000000..44e841efd
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
differ
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-4.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-4.jpeg"
new file mode 100644
index 000000000..d4fcd2c70
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-4.jpeg"
differ
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-5.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-5.jpeg"
new file mode 100644
index 000000000..4f2e99226
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/current/picture/4.x\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-5.jpeg"
differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ
Prometheus Exporter - 2.jpeg
b/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ Prometheus
Exporter - 2.jpeg
new file mode 100644
index 000000000..8243169b1
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ Prometheus
Exporter - 2.jpeg differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ
Prometheus Exporter-1.jpeg
b/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ Prometheus
Exporter-1.jpeg
new file mode 100644
index 000000000..b894b6db0
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ Prometheus
Exporter-1.jpeg differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ
Prometheus Exporter-3.jpeg
b/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ Prometheus
Exporter-3.jpeg
new file mode 100644
index 000000000..f0f9ac2f1
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/current/picture/RocketMQ Prometheus
Exporter-3.jpeg differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/05Exporter.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/05Exporter.md
index d75ebc48b..78e7b2683 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/05Exporter.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/05Exporter.md
@@ -8,7 +8,7 @@ In previous versions, there were 87 concurrentHashMaps, but
since the Map does n
:::
The process for `Rocketmq-exporter` to obtain monitoring metrics is shown in
the following figure. The exporter requests data from the MQ cluster through
MQAdminExt, and the requested data is standardized into the format required by
Prometheus through the MetricService, and then exposed to Promethus through the
`/metrics` interface.
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l5ui30u2j21dy0u076k.jpg";></img>
+
### Metric structure
@@ -127,7 +127,7 @@ The MetricCollectTask class has five scheduled tasks:
collectTopicOffset, collec
### Rocketmq-exporter collects metrics flowchart
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l64nrfwrj20oz0btmze.jpg";></img>
+
## Quick star
@@ -155,7 +155,7 @@ Configure Prometheus's static_config: -targets to the
exporter's starting IP and
If the localhost starts at the default localhost:9090, you can view the
collected metric values, as shown in the following figure:
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l66aaa7tj215y0bzwi0.jpg";></img>
+
:::tip
For better visualization effects and to observe the trend of metric value
changes, Prometheus is better used with Grafana!
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05subscribe.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05subscribe.md
index 1d852ba09..0c3b5b1a0 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05subscribe.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/06-bestPractice/05subscribe.md
@@ -12,7 +12,7 @@ Subscription relationships are consistent when all Consumer
instances in the sam
As shown in the following figure, the three Consumer instances C1, C2, and C3
in the same ConsumerGroup have all subscribed to TopicA, and the subscriptions
to TopicA's Tag are all Tag1, which meets the principle of subscription
relationship consistency.
-
+
**Correct example code 1:**
@@ -60,13 +60,13 @@ In the early 3.x/4.x versions of the SDK, as shown in the
following figure, thre
:::note
The 5.x version of the SDK now supports Consumer instances in the same
ConsumerGroup subscribing to different topics.
:::
-
+
### 3.2 Consumer instances in the same ConsumerGroup subscribe to the same
topic, but the subscribed tags are different.
As shown in the following figure, the Consumer instances C1, C2, and C3 in the
same ConsumerGroup all subscribe to TopicA, but C1 subscribes to Tag1 of
TopicA, while C2 and C3 subscribe to Tag2 of TopicA. The subscribed tags of the
same topic are inconsistent and do not conform to the consistency principle of
subscription relationship.
-
+
**Error example code 2:**
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
new file mode 100644
index 000000000..bdf30130b
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
differ
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
new file mode 100644
index 000000000..d4fcd2c70
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
differ
diff --git
"a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
"b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
new file mode 100644
index 000000000..4f2e99226
Binary files /dev/null and
"b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter - 2.jpeg
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter - 2.jpeg
new file mode 100644
index 000000000..8243169b1
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter - 2.jpeg differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter-1.jpeg
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter-1.jpeg
new file mode 100644
index 000000000..b894b6db0
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter-1.jpeg differ
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter-3.jpeg
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter-3.jpeg
new file mode 100644
index 000000000..f0f9ac2f1
Binary files /dev/null and
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/picture/RocketMQ
Prometheus Exporter-3.jpeg differ
diff --git a/src/pages/contact.md b/src/pages/contact.md
index b03a054f9..2a72fa460 100644
--- a/src/pages/contact.md
+++ b/src/pages/contact.md
@@ -3,7 +3,7 @@
## 1. Follow Apache RocketMQ Wechat Account
-
+
diff --git a/src/pages/version 2.md b/src/pages/version 2.md
index f91fb17f8..97b599ba6 100644
--- a/src/pages/version 2.md
+++ b/src/pages/version 2.md
@@ -5,7 +5,7 @@ Apache RocketMQ 自诞生以来，因其架构简单、业务功能丰富、具
集成效率的痛点升级优化：从API、SDK多方面重构设计，为开发者提供更加简单易用、轻量易集成的方案；
事件、流集成场景拓宽：我们将以当前业务集成的能力为基础进一步聚焦消息领域的后处理场景，支持消息的流式处理和轻计算，帮助用户实现消息的就近计算和分析，并将全面拥抱
Serverless 和 EDA。
-
+
## What's New in RocketMQ 5.0
@@ -13,7 +13,7 @@ Apache RocketMQ 自诞生以来，因其架构简单、业务功能丰富、具
RocketMQ 自诞生以来就一直坚持简洁架构，比如元数据采用最终一致性设计，只引入了几百行代码的无状态 NameSrv 组件。相比其他产品依赖 ZK
进行元数据的管理维护，RocketMQ 的优势是显而易见的。
随着企业上云的进一步普及以及云原生技术趋势的演进，集成的网络环境更加复杂，企业开发者对效率也有了更高的要求，我们看到当前的架构还存在一定的不足。当前的架构下存储和计算资源的灵活匹配相对困难，特别是在如今企业上云逐步普及的情况下，云厂商的计算资源和存储资源之间解耦灵活的弹性策略可以更好的实现降本提效。
-
+
RocketMQ 5.0
引入了全新的弹性无状态代理模式，将当前的Broker职责进行拆分，对于客户端协议适配、权限管理、消费管理等计算逻辑进行抽离，独立无状态的代理角色提供服务，Broker则继续专注于存储能力的持续优化。这套模式可以更好地实现在云环境的资源弹性调度。
值得注意的是RocketMQ
5.0的全新模式是和4.0的极简架构模式相容相通的，5.0的代理架构完全可以以Local模式运行，实现与4.0架构完全一致的效果。开发者可以根据自身的业务场景自由选择架构部署。
@@ -21,7 +21,7 @@ RocketMQ 5.0 引入了全新的弹性无状态代理模式，将当前的Broker
### 轻量API和多语言SDK
除了架构改变，RocketMQ 5.0 重新思考了面向开发者的集成界面，即API和SDK的设计。RocketMQ 4.x SDK
是比较重量级的富客户端模式，提供了诸如顺序消费、广播消费、消费者负载均衡、消息缓存、消息重试、位点管理、推拉结合、流控、诊断、故障转移、异常节点隔离等一系列能力。这些复杂能力虽然可以帮助业务集成解决实际问题，但其自身的演进和迭代却存在比较大的负担，客户端的升级和多语言普及难度较大。从API的简洁性和友好性方面，RocketMQ
5.0正在做轻量化设计。
-
+
RocketMQ 5.0 推出了基于 gRPC 全新的多语言 SDK，这套 SDK 有几个重要特点：
采用全新极简的 API，拥有不可变 API 的设计，完善的错误处理，各语言 SDK API 在本地语言层面对齐，新的API 化繁为简，更易被使用和集成。
@@ -34,20 +34,20 @@ RocketMQ 5.0 推出了基于 gRPC 全新的多语言 SDK，这套 SDK 有几个
除了上述基础架构以及API集成的变化，RocketMQ 5.0基于业务消息的基础优势，RocketMQ
5.0进一步拓宽在消息后处理计算的场景挖掘。支持消息的流式处理和轻计算，帮助用户实现消息的就近计算和分析，并将全面拥抱 Serverless 和 EDA。
-
+
伴随企业云原生化进程的加速，计算力的构成越来越多样化，通过事件驱动架构来开发云原生应用是一件非常顺理成章的事情。RocketMQ 5.0
正是基于此技术趋势大潮开放了兼容标准CloudEvents协议的RocketMQ-EventBridge组件。EventBridge提供丰富的跨产品、跨平台连接能力，能够促进云厂商、企业应用、SaaS
服务三者相互集成。EventBridge的目标是以统一开放的标准链接社区活跃的生态，同时能与各个云厂商的「Hub」类产品进行集成，来达到开源和云的数据互通，助力企业客户轻松上云和下云。
-
+
在消息流式处理场景，RocketMQ
5.0将当前的队列下沉为物理队列，上层重新抽象了逻辑队列。一个逻辑队列可以包含多个物理队列，各个物理队列都作为逻辑队列的一个片段，以此拼接出真正的流式队列。也因此可以做到更轻量，秒级扩缩，在物理节点发生变化时不涉及到存量数据复制迁移；实现数据存储的灵活调度，配合
TTL 实现无限存储能力。同时，应对流的高吞吐场景，RocketMQ 5.0优化里存储批量处理的读写性能。
-
+
在计算框架方面，RocketMQ 5.0 引入了一套轻量级流式处理框架RSteams。RStreams 依赖少、部署简单，可任意横向扩展，利用
RocketMQ 资源即可完成轻量级的数据处理和计算。除此以外，为了方便开发者让基于 RocketMQ 的流式计算更容易，RocketMQ 5.0
还支持了一套轻量SQL查询引擎 RSQLDB，为开发者提供基于 SQL 的开发体验。RSQLDB 首创性地兼容了 Flink/Blink SQL 标准以及
UDF/UDAF/UDTF，使得两个开源产品的生态可以更好地融合，开发者可以将 Flink/Blink 已有 SQL 计算任务迁移到 RocketMQ ，在
RocketMQ 内部完成轻量级的计算处理，在算力受限或者更大规模的场景下，同样可以将 RocketMQ 的实时计算任务迁移到 Flink，利用 Flink
的大数据计算能力满足业务诉求。
## How to upgrade to 5.0
RocketMQ 5.0在完成上述架构升级、API重构和新功能场景时，统一遵循了向下兼容的原则。RocketMQ
4.x版本可以无缝升级到5.0版本同时保持对历史版本SDK的兼容。选择5.0版本无需担心不兼容历史版本的应用。我们建议升级服务端版本后，尽快替换使用新版本的SDK以获得更好的接入体验和新功能。
-
+
diff --git a/src/pages/version.md b/src/pages/version.md
index f91fb17f8..97b599ba6 100644
--- a/src/pages/version.md
+++ b/src/pages/version.md
@@ -5,7 +5,7 @@ Apache RocketMQ 自诞生以来，因其架构简单、业务功能丰富、具
集成效率的痛点升级优化：从API、SDK多方面重构设计，为开发者提供更加简单易用、轻量易集成的方案；
事件、流集成场景拓宽：我们将以当前业务集成的能力为基础进一步聚焦消息领域的后处理场景，支持消息的流式处理和轻计算，帮助用户实现消息的就近计算和分析，并将全面拥抱
Serverless 和 EDA。
-
+
## What's New in RocketMQ 5.0
@@ -13,7 +13,7 @@ Apache RocketMQ 自诞生以来，因其架构简单、业务功能丰富、具
RocketMQ 自诞生以来就一直坚持简洁架构，比如元数据采用最终一致性设计，只引入了几百行代码的无状态 NameSrv 组件。相比其他产品依赖 ZK
进行元数据的管理维护，RocketMQ 的优势是显而易见的。
随着企业上云的进一步普及以及云原生技术趋势的演进，集成的网络环境更加复杂，企业开发者对效率也有了更高的要求，我们看到当前的架构还存在一定的不足。当前的架构下存储和计算资源的灵活匹配相对困难，特别是在如今企业上云逐步普及的情况下，云厂商的计算资源和存储资源之间解耦灵活的弹性策略可以更好的实现降本提效。
-
+
RocketMQ 5.0
引入了全新的弹性无状态代理模式，将当前的Broker职责进行拆分，对于客户端协议适配、权限管理、消费管理等计算逻辑进行抽离，独立无状态的代理角色提供服务，Broker则继续专注于存储能力的持续优化。这套模式可以更好地实现在云环境的资源弹性调度。
值得注意的是RocketMQ
5.0的全新模式是和4.0的极简架构模式相容相通的，5.0的代理架构完全可以以Local模式运行，实现与4.0架构完全一致的效果。开发者可以根据自身的业务场景自由选择架构部署。
@@ -21,7 +21,7 @@ RocketMQ 5.0 引入了全新的弹性无状态代理模式，将当前的Broker
### 轻量API和多语言SDK
除了架构改变，RocketMQ 5.0 重新思考了面向开发者的集成界面，即API和SDK的设计。RocketMQ 4.x SDK
是比较重量级的富客户端模式，提供了诸如顺序消费、广播消费、消费者负载均衡、消息缓存、消息重试、位点管理、推拉结合、流控、诊断、故障转移、异常节点隔离等一系列能力。这些复杂能力虽然可以帮助业务集成解决实际问题，但其自身的演进和迭代却存在比较大的负担，客户端的升级和多语言普及难度较大。从API的简洁性和友好性方面，RocketMQ
5.0正在做轻量化设计。
-
+
RocketMQ 5.0 推出了基于 gRPC 全新的多语言 SDK，这套 SDK 有几个重要特点：
采用全新极简的 API，拥有不可变 API 的设计，完善的错误处理，各语言 SDK API 在本地语言层面对齐，新的API 化繁为简，更易被使用和集成。
@@ -34,20 +34,20 @@ RocketMQ 5.0 推出了基于 gRPC 全新的多语言 SDK，这套 SDK 有几个
除了上述基础架构以及API集成的变化，RocketMQ 5.0基于业务消息的基础优势，RocketMQ
5.0进一步拓宽在消息后处理计算的场景挖掘。支持消息的流式处理和轻计算，帮助用户实现消息的就近计算和分析，并将全面拥抱 Serverless 和 EDA。
-
+
伴随企业云原生化进程的加速，计算力的构成越来越多样化，通过事件驱动架构来开发云原生应用是一件非常顺理成章的事情。RocketMQ 5.0
正是基于此技术趋势大潮开放了兼容标准CloudEvents协议的RocketMQ-EventBridge组件。EventBridge提供丰富的跨产品、跨平台连接能力，能够促进云厂商、企业应用、SaaS
服务三者相互集成。EventBridge的目标是以统一开放的标准链接社区活跃的生态，同时能与各个云厂商的「Hub」类产品进行集成，来达到开源和云的数据互通，助力企业客户轻松上云和下云。
-
+
在消息流式处理场景，RocketMQ
5.0将当前的队列下沉为物理队列，上层重新抽象了逻辑队列。一个逻辑队列可以包含多个物理队列，各个物理队列都作为逻辑队列的一个片段，以此拼接出真正的流式队列。也因此可以做到更轻量，秒级扩缩，在物理节点发生变化时不涉及到存量数据复制迁移；实现数据存储的灵活调度，配合
TTL 实现无限存储能力。同时，应对流的高吞吐场景，RocketMQ 5.0优化里存储批量处理的读写性能。
-
+
在计算框架方面，RocketMQ 5.0 引入了一套轻量级流式处理框架RSteams。RStreams 依赖少、部署简单，可任意横向扩展，利用
RocketMQ 资源即可完成轻量级的数据处理和计算。除此以外，为了方便开发者让基于 RocketMQ 的流式计算更容易，RocketMQ 5.0
还支持了一套轻量SQL查询引擎 RSQLDB，为开发者提供基于 SQL 的开发体验。RSQLDB 首创性地兼容了 Flink/Blink SQL 标准以及
UDF/UDAF/UDTF，使得两个开源产品的生态可以更好地融合，开发者可以将 Flink/Blink 已有 SQL 计算任务迁移到 RocketMQ ，在
RocketMQ 内部完成轻量级的计算处理，在算力受限或者更大规模的场景下，同样可以将 RocketMQ 的实时计算任务迁移到 Flink，利用 Flink
的大数据计算能力满足业务诉求。
## How to upgrade to 5.0
RocketMQ 5.0在完成上述架构升级、API重构和新功能场景时，统一遵循了向下兼容的原则。RocketMQ
4.x版本可以无缝升级到5.0版本同时保持对历史版本SDK的兼容。选择5.0版本无需担心不兼容历史版本的应用。我们建议升级服务端版本后，尽快替换使用新版本的SDK以获得更好的接入体验和新功能。
-
+
diff --git "a/static/img/5.0\351\200\237\350\247\210-1.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-1.jpeg"
new file mode 100644
index 000000000..b1046904c
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-1.jpeg"
differ
diff --git "a/static/img/5.0\351\200\237\350\247\210-2.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-2.jpeg"
new file mode 100644
index 000000000..25f88ed4d
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-2.jpeg"
differ
diff --git "a/static/img/5.0\351\200\237\350\247\210-3.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-3.jpeg"
new file mode 100644
index 000000000..3cb09919d
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-3.jpeg"
differ
diff --git "a/static/img/5.0\351\200\237\350\247\210-4.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-4.jpeg"
new file mode 100644
index 000000000..eb4baafa0
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-4.jpeg"
differ
diff --git "a/static/img/5.0\351\200\237\350\247\210-5.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-5.jpeg"
new file mode 100644
index 000000000..2f11d30d3
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-5.jpeg"
differ
diff --git "a/static/img/5.0\351\200\237\350\247\210-6.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-6.jpeg"
new file mode 100644
index 000000000..de188b192
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-6.jpeg"
differ
diff --git "a/static/img/5.0\351\200\237\350\247\210-7.jpeg"
"b/static/img/5.0\351\200\237\350\247\210-7.jpeg"
new file mode 100644
index 000000000..f6fac79f3
Binary files /dev/null and "b/static/img/5.0\351\200\237\350\247\210-7.jpeg"
differ
diff --git a/static/img/contact.jpeg b/static/img/contact.jpeg
new file mode 100644
index 000000000..a110d26fa
Binary files /dev/null and b/static/img/contact.jpeg differ
diff --git a/versioned_docs/version-5.0/05-deploymentOperations/05Exporter.md
b/versioned_docs/version-5.0/05-deploymentOperations/05Exporter.md
index 79bdaf5c9..1136f465c 100644
--- a/versioned_docs/version-5.0/05-deploymentOperations/05Exporter.md
+++ b/versioned_docs/version-5.0/05-deploymentOperations/05Exporter.md
@@ -9,7 +9,7 @@
:::
`Rocketmq-expoter` 获取监控指标的流程如下图所示，Expoter 通过 MQAdminExt 向 MQ 集群请求数据，请求到的数据通过
MetricService 规范化成 Prometheus 需要的格式，然后通过 /metics 接口暴露给 Promethus。
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l5ui30u2j21dy0u076k.jpg";></img>
+
@@ -130,7 +130,7 @@ MetricCollectTask 类中有 5 个定时任务，分别为 collectTopicOffset、c
### Rocketmq-exporter 收集指标流程图
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l64nrfwrj20oz0btmze.jpg";></img>
+
## 快速开始
@@ -158,7 +158,7 @@ MetricCollectTask 类中有 5 个定时任务，分别为 collectTopicOffset、c
本地启动默认为: localhost:9090 ,则可对收集到的指标值进行查看,如下图所示:
-<img
src="https://tva1.sinaimg.cn/large/e6c9d24egy1h4l66aaa7tj215y0bzwi0.jpg";></img>
+
:::tip
diff --git a/versioned_docs/version-5.0/06-bestPractice/05subscribe.md
b/versioned_docs/version-5.0/06-bestPractice/05subscribe.md
index 8c237124c..5536f502b 100644
--- a/versioned_docs/version-5.0/06-bestPractice/05subscribe.md
+++ b/versioned_docs/version-5.0/06-bestPractice/05subscribe.md
@@ -12,7 +12,7 @@
如下图所示，同一 ConsumerGroup
下的三个Consumer实例C1、C2和C3分别都订阅了TopicA，且订阅TopicA的Tag也都是Tag1，符合订阅关系一致原则。
-
+
**正确示例代码一**
@@ -61,13 +61,13 @@ RocketMQ 强调订阅关系一致，核心是指相同 ConsumerGroup 的每个 C
:::note
5.x版本SDK 已经支持同一个 ConsumerGroup 下的Consumer实例订阅不同的Topic。
:::
-
+
### 3.2 同一 ConsumerGroup 下的 Consumer 实例订阅的Topic相同，但订阅的Tag不一致
如下图所示，同一 ConsumerGroup
下的三个Consumer实例C1、C2和C3分别都订阅了TopicA，但是C1订阅TopicA的Tag为**Tag1**，C2和C3订阅的TopicA的Tag为**Tag2**，订阅同一Topic的Tag不一致，不符合订阅关系一致性原则。
-
+
**错误示例代码二**
diff --git
"a/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
"b/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
new file mode 100644
index 000000000..bdf30130b
Binary files /dev/null and
"b/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-1.jpeg"
differ
diff --git
"a/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
"b/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
new file mode 100644
index 000000000..d4fcd2c70
Binary files /dev/null and
"b/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-2.jpeg"
differ
diff --git
"a/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
"b/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
new file mode 100644
index 000000000..4f2e99226
Binary files /dev/null and
"b/versioned_docs/version-5.0/picture/5.0\350\256\242\351\230\205\345\205\263\347\263\273\344\270\200\350\207\264-3.jpeg"
differ
diff --git a/versioned_docs/version-5.0/picture/RocketMQ Prometheus Exporter -
2.jpeg b/versioned_docs/version-5.0/picture/RocketMQ Prometheus Exporter -
2.jpeg
new file mode 100644
index 000000000..8243169b1
Binary files /dev/null and b/versioned_docs/version-5.0/picture/RocketMQ
Prometheus Exporter - 2.jpeg differ
diff --git a/versioned_docs/version-5.0/picture/RocketMQ Prometheus
Exporter-1.jpeg b/versioned_docs/version-5.0/picture/RocketMQ Prometheus
Exporter-1.jpeg
new file mode 100644
index 000000000..b894b6db0
Binary files /dev/null and b/versioned_docs/version-5.0/picture/RocketMQ
Prometheus Exporter-1.jpeg differ
diff --git a/versioned_docs/version-5.0/picture/RocketMQ Prometheus
Exporter-3.jpeg b/versioned_docs/version-5.0/picture/RocketMQ Prometheus
Exporter-3.jpeg
new file mode 100644
index 000000000..f0f9ac2f1
Binary files /dev/null and b/versioned_docs/version-5.0/picture/RocketMQ
Prometheus Exporter-3.jpeg differ
![https://tva1.sinaimg.cn/large/e6c9d24egy1h4l5ui30u2j21dy0u076k.jpg"](https://tva1.sinaimg.cn/large/e6c9d24egy1h4l5ui30u2j21dy0u076k.jpg"){kind=link}
![https://tva1.sinaimg.cn/large/e6c9d24egy1h4l64nrfwrj20oz0btmze.jpg"](https://tva1.sinaimg.cn/large/e6c9d24egy1h4l64nrfwrj20oz0btmze.jpg"){kind=link}
![https://tva1.sinaimg.cn/large/e6c9d24egy1h4l66aaa7tj215y0bzwi0.jpg"](https://tva1.sinaimg.cn/large/e6c9d24egy1h4l66aaa7tj215y0bzwi0.jpg"){kind=link}
