This is an automated email from the ASF dual-hosted git repository.
dengliming pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shenyu-website.git
The following commit(s) were added to refs/heads/main by this push:
new a87ce25d38b Fix image not displaying (#1096)
a87ce25d38b is described below
commit a87ce25d38b19320e60229ded51795ce9c50c76d
Author: L <[email protected]>
AuthorDate: Thu Nov 20 10:16:53 2025 +0800
Fix image not displaying (#1096)
Co-authored-by: [email protected] <2823602869Zxy@>
---
docs/design/data-sync.md | 2 +-
.../current/design/data-sync.md | 2 +-
.../version-2.3.0-Legacy/design/data-sync.md | 3 +--
.../version-2.4.0/design/data-sync.md | 2 +-
.../version-2.4.1/design/data-sync.md | 2 +-
.../version-2.4.2/design/data-sync.md | 2 +-
.../version-2.4.3/design/data-sync.md | 2 +-
.../version-2.5.0/design/data-sync.md | 2 +-
.../version-2.5.1/design/data-sync.md | 2 +-
.../version-2.6.0/design/data-sync.md | 2 +-
.../version-2.6.1/design/data-sync.md | 2 +-
.../version-2.7.0.1/design/data-sync.md | 2 +-
.../version-2.7.0.2/design/data-sync.md | 2 +-
.../version-2.7.0/design/data-sync.md | 2 +-
.../img/shenyu/dataSync/shenyu-data-sync-zookeeper.png | Bin 0 -> 97717 bytes
versioned_docs/version-2.3.0-Legacy/design/data-sync.md | 2 +-
versioned_docs/version-2.4.0/design/data-sync.md | 2 +-
versioned_docs/version-2.4.1/design/data-sync.md | 2 +-
versioned_docs/version-2.4.2/design/data-sync.md | 2 +-
versioned_docs/version-2.4.3/design/data-sync.md | 2 +-
versioned_docs/version-2.5.0/design/data-sync.md | 2 +-
versioned_docs/version-2.5.1/design/data-sync.md | 2 +-
versioned_docs/version-2.6.0/design/data-sync.md | 2 +-
versioned_docs/version-2.6.1/design/data-sync.md | 2 +-
versioned_docs/version-2.7.0.1/design/data-sync.md | 2 +-
versioned_docs/version-2.7.0.2/design/data-sync.md | 2 +-
versioned_docs/version-2.7.0/design/data-sync.md | 2 +-
27 files changed, 26 insertions(+), 27 deletions(-)
diff --git a/docs/design/data-sync.md b/docs/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/docs/design/data-sync.md
+++ b/docs/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/current/design/data-sync.md
index 816e3c21296..3d8563af027 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0-Legacy/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0-Legacy/design/data-sync.md
index ddac3628a1f..28dc59a9c82 100755
---
a/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0-Legacy/design/data-sync.md
+++
b/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0-Legacy/design/data-sync.md
@@ -49,8 +49,7 @@ soul作为网关，为了提供更高的响应速度，所有的配置都缓存
基于 zookeeper 的同步原理很简单，主要是依赖 `zookeeper` 的 watch 机制，`soul-web`
会监听配置的节点，`soul-admin` 在启动的时候，会将数据全量写入 `zookeeper`，后续数据发生变更时，会增量更新 `zookeeper`
的节点，与此同时，`soul-web` 会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
-
+
`soul` 将配置信息写到zookeeper节点，是通过精细设计的。
## Websocket同步
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/design/data-sync.md
index c9282add1ee..21d8b527dc2 100755
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `zookeeper` 的同步原理很简单，主要是依赖 `zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `zookeeper`，后续数据发生变更时，会增量更新
`zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/design/data-sync.md
index 78968d0d5b4..2747fb2060e 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `zookeeper` 的同步原理很简单，主要是依赖 `zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `zookeeper`，后续数据发生变更时，会增量更新
`zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/design/data-sync.md
index 444504cdc55..7ef9270a481 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `zookeeper` 的同步原理很简单，主要是依赖 `zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `zookeeper`，后续数据发生变更时，会增量更新
`zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/design/data-sync.md
index 319172421f6..28c1316cb2b 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `zookeeper` 的同步原理很简单，主要是依赖 `zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `zookeeper`，后续数据发生变更时，会增量更新
`zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.5.0/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.5.0/design/data-sync.md
index ff6049fb5b4..8eaf03a57e2 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.5.0/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.5.0/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.5.1/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.5.1/design/data-sync.md
index 816e3c21296..3d8563af027 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.5.1/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.5.1/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.0/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.0/design/data-sync.md
index 816e3c21296..3d8563af027 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.0/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.0/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/data-sync.md
index 816e3c21296..3d8563af027 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6.1/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.1/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.1/design/data-sync.md
index 1a1f0dbe209..869609ca4bf 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.1/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.1/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.2/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.2/design/data-sync.md
index 1a1f0dbe209..869609ca4bf 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.2/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0.2/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git
a/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0/design/data-sync.md
b/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0/design/data-sync.md
index 816e3c21296..3d8563af027 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0/design/data-sync.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.7.0/design/data-sync.md
@@ -52,7 +52,7 @@ description: 数据同步
基于 `Zookeeper` 的同步原理很简单，主要是依赖 `Zookeeper` 的 `watch` 机制。`Apache
ShenYu`网关会监听配置的节点，`shenyu-admin` 在启动的时候，会将数据全量写入 `Zookeeper`，后续数据发生变更时，会增量更新
`Zookeeper` 的节点，与此同时，`Apache ShenYu`网关会监听配置信息的节点，一旦有信息变更时，会更新本地缓存。
-
+
`Apache ShenYu` 将配置信息写到`zookeeper`节点，是通过精心设计的，如果您想深入了解代码实现，请参考源码
`ZookeeperSyncDataService`。
diff --git a/static/img/shenyu/dataSync/shenyu-data-sync-zookeeper.png
b/static/img/shenyu/dataSync/shenyu-data-sync-zookeeper.png
new file mode 100644
index 00000000000..81142f18121
Binary files /dev/null and
b/static/img/shenyu/dataSync/shenyu-data-sync-zookeeper.png differ
diff --git a/versioned_docs/version-2.3.0-Legacy/design/data-sync.md
b/versioned_docs/version-2.3.0-Legacy/design/data-sync.md
index 1445d4b803d..e7de4016a29 100755
--- a/versioned_docs/version-2.3.0-Legacy/design/data-sync.md
+++ b/versioned_docs/version-2.3.0-Legacy/design/data-sync.md
@@ -49,7 +49,7 @@ As showing picture below,`soul-admin` will issue a
configuration change notifica
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`soul-web` will monitor the configured node,when
`soul-admin` starts,all the data will be written to `zookeeper`,it will
incrementally update the nodes of `zookeeper` when data changes,at the same
time, `soul-web` will monitor the node for configuration information, and
update the local cache once the information changes
-
+
`soul` writes the configuration information to the zookeeper node,and it is
meticulously designed.
diff --git a/versioned_docs/version-2.4.0/design/data-sync.md
b/versioned_docs/version-2.4.0/design/data-sync.md
index 9d7843c4e2a..ae8429fd97b 100755
--- a/versioned_docs/version-2.4.0/design/data-sync.md
+++ b/versioned_docs/version-2.4.0/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.4.1/design/data-sync.md
b/versioned_docs/version-2.4.1/design/data-sync.md
index c129baf93fa..56c0fa673e4 100644
--- a/versioned_docs/version-2.4.1/design/data-sync.md
+++ b/versioned_docs/version-2.4.1/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.4.2/design/data-sync.md
b/versioned_docs/version-2.4.2/design/data-sync.md
index c129baf93fa..56c0fa673e4 100644
--- a/versioned_docs/version-2.4.2/design/data-sync.md
+++ b/versioned_docs/version-2.4.2/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.4.3/design/data-sync.md
b/versioned_docs/version-2.4.3/design/data-sync.md
index c129baf93fa..56c0fa673e4 100644
--- a/versioned_docs/version-2.4.3/design/data-sync.md
+++ b/versioned_docs/version-2.4.3/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.5.0/design/data-sync.md
b/versioned_docs/version-2.5.0/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.5.0/design/data-sync.md
+++ b/versioned_docs/version-2.5.0/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.5.1/design/data-sync.md
b/versioned_docs/version-2.5.1/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.5.1/design/data-sync.md
+++ b/versioned_docs/version-2.5.1/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.6.0/design/data-sync.md
b/versioned_docs/version-2.6.0/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.6.0/design/data-sync.md
+++ b/versioned_docs/version-2.6.0/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.6.1/design/data-sync.md
b/versioned_docs/version-2.6.1/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.6.1/design/data-sync.md
+++ b/versioned_docs/version-2.6.1/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.7.0.1/design/data-sync.md
b/versioned_docs/version-2.7.0.1/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.7.0.1/design/data-sync.md
+++ b/versioned_docs/version-2.7.0.1/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.7.0.2/design/data-sync.md
b/versioned_docs/version-2.7.0.2/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.7.0.2/design/data-sync.md
+++ b/versioned_docs/version-2.7.0.2/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
diff --git a/versioned_docs/version-2.7.0/design/data-sync.md
b/versioned_docs/version-2.7.0/design/data-sync.md
index e1256f7c52f..2a7baa670d8 100644
--- a/versioned_docs/version-2.7.0/design/data-sync.md
+++ b/versioned_docs/version-2.7.0/design/data-sync.md
@@ -66,7 +66,7 @@ As showing picture below,`shenyu-admin` will issue a
configuration change notifi
The zookeeper-based synchronization principle is very simple,it mainly depends
on `zookeeper` watch mechanism,`shenyu-web` will monitor the configured
node,when `shenyu-admin` starts,all the data will be written to `zookeeper`,it
will incrementally update the nodes of `zookeeper` when data changes,at the
same time, `shenyu-web` will monitor the node for configuration information,
and update the local cache once the information changes
-
+
`Apache ShenYu` writes the configuration information to the zookeeper node,and
it is meticulously designed. If you want to learn more about the code
implementation, refer to the source code `ZookeeperSyncDataService`.
