This is an automated email from the ASF dual-hosted git repository.
jianbin pushed a commit to branch docusaurus
in repository https://gitbox.apache.org/repos/asf/incubator-seata-website.git
The following commit(s) were added to refs/heads/docusaurus by this push:
new 4e8af6c696c update namingserver.md (#1015)
4e8af6c696c is described below
commit 4e8af6c696cc67337d470bcff9b2ddbf4efe516f
Author: funkye <[email protected]>
AuthorDate: Mon Aug 25 15:46:03 2025 +0800
update namingserver.md (#1015)
---
.../current/user/registry/namingserver.md | 16 +++++++++-------
.../version-v2.4/user/registry/namingserver.md | 13 +++++++------
.../version-v2.5/user/registry/namingserver.md | 16 +++++++++-------
.../current/user/registry/namingserver.md | 5 ++++-
.../version-v2.4/user/registry/namingserver.md | 3 ++-
.../version-v2.5/user/registry/namingserver.md | 5 ++++-
6 files changed, 35 insertions(+), 23 deletions(-)
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
b/i18n/en/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
index 7e65146fedc..a65f85dbd3e 100644
---
a/i18n/en/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
+++
b/i18n/en/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
@@ -129,27 +129,29 @@ You'll receive a response like this. Copy the data field
for use in the `authori
}
```
-### Creating a Transaction Group to Seata Cluster Mapping
+### Create the client transaction-group -> Seata cluster mapping
-Send an HTTP request to a namingserver node to create a transaction group
mapping relationship (the namingserver node will automatically synchronize with
other nodes):
+Start the namingserver, then start the Seata Server.
+
+Send an HTTP request to a namingserver node to create the transaction-group
mapping (the namingserver node will automatically synchronize it to other
nodes):
```shell
curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/addGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group
```
-(Where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the cluster name
of the server to map to)
+(where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the Seata Server
cluster to map to)
-### Switching Transaction Group to Seata Cluster Mapping (Traffic Switching)
+### Switch the client transaction-group -> Seata cluster mapping (cutover)
-Send an HTTP request to a namingserver node to modify the transaction group
mapping relationship:
+Send an HTTP request to a namingserver node to modify the transaction-group
mapping (the namingserver node will automatically synchronize it to other
nodes):
```shell
curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/changeGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group
```
-(Where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the cluster name
of the server to map to)
+(where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the Seata Server
cluster to map to)
-After starting Seata-Server and configuring the client, you can start your
application and begin using Seata services.
+If there is no Seata Server available under the specified namespace and
clusterName when creating the transaction group, creation will fail. After
configuring the client and starting your application, you can start using Seata
services.
Tips:
- 1. Ensure the client and server registries are in the same namespace,
otherwise services won't be found.
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
b/i18n/en/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
index 7e65146fedc..e6f08e2e326 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
@@ -131,25 +131,26 @@ You'll receive a response like this. Copy the data field
for use in the `authori
### Creating a Transaction Group to Seata Cluster Mapping
-Send an HTTP request to a namingserver node to create a transaction group
mapping relationship (the namingserver node will automatically synchronize with
other nodes):
+Start the namingserver first, then start Seata-Server.
+Send an HTTP request to a namingserver node to create a mapping between a
transaction group and a Seata cluster (the namingserver node will automatically
synchronize the change to other nodes):
```shell
curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/addGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group
```
-(Where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the cluster name
of the server to map to)
+(where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the server
cluster to map to)
-### Switching Transaction Group to Seata Cluster Mapping (Traffic Switching)
+### Switching the client transaction group -> Seata cluster mapping (traffic
switching)
-Send an HTTP request to a namingserver node to modify the transaction group
mapping relationship:
+Send an HTTP request to a namingserver node to modify the transaction group
mapping (the namingserver node will automatically synchronize the change to
other nodes):
```shell
curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/changeGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group
```
-(Where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the cluster name
of the server to map to)
+(where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the server
cluster to map to)
-After starting Seata-Server and configuring the client, you can start your
application and begin using Seata services.
+After the client configuration is complete and the application is started, you
can begin using Seata services.
Tips:
- 1. Ensure the client and server registries are in the same namespace,
otherwise services won't be found.
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
b/i18n/en/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
index 7e65146fedc..a65f85dbd3e 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
@@ -129,27 +129,29 @@ You'll receive a response like this. Copy the data field
for use in the `authori
}
```
-### Creating a Transaction Group to Seata Cluster Mapping
+### Create the client transaction-group -> Seata cluster mapping
-Send an HTTP request to a namingserver node to create a transaction group
mapping relationship (the namingserver node will automatically synchronize with
other nodes):
+Start the namingserver, then start the Seata Server.
+
+Send an HTTP request to a namingserver node to create the transaction-group
mapping (the namingserver node will automatically synchronize it to other
nodes):
```shell
curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/addGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group
```
-(Where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the cluster name
of the server to map to)
+(where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the Seata Server
cluster to map to)
-### Switching Transaction Group to Seata Cluster Mapping (Traffic Switching)
+### Switch the client transaction-group -> Seata cluster mapping (cutover)
-Send an HTTP request to a namingserver node to modify the transaction group
mapping relationship:
+Send an HTTP request to a namingserver node to modify the transaction-group
mapping (the namingserver node will automatically synchronize it to other
nodes):
```shell
curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/changeGroup?clusterName=cluster2&namespace=public&unitName&vGroup=my_test_tx_group
```
-(Where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the cluster name
of the server to map to)
+(where namespace is the namespace configured on the client, vGroup is the
transaction group configured on the client, and clusterName is the Seata Server
cluster to map to)
-After starting Seata-Server and configuring the client, you can start your
application and begin using Seata services.
+If there is no Seata Server available under the specified namespace and
clusterName when creating the transaction group, creation will fail. After
configuring the client and starting your application, you can start using Seata
services.
Tips:
- 1. Ensure the client and server registries are in the same namespace,
otherwise services won't be found.
diff --git
a/i18n/zh-cn/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
b/i18n/zh-cn/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
index 6111ab0ac31..5b4b4845a1d 100644
---
a/i18n/zh-cn/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
+++
b/i18n/zh-cn/docusaurus-plugin-content-docs/current/user/registry/namingserver.md
@@ -129,6 +129,8 @@ curl -X POST http://localhost:8081/api/v1/auth/login \
### 创建client端的事务分组->seata集群的映射关系
+先启动namingserver,随后,启动 Seata-Server
+
向一个namingserver节点发起创建事务分组映射关系的http请求（namingserver节点会自动同步给其它节点）
```shell
@@ -147,7 +149,8 @@ curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/
（其中namespace是client端配置的命名空间，vGroup是client端配置的事务分组，clusterName是需要映射到的server端的集群名称）
-随后,启动 Seata-Server 后，Client 配置完成后启动应用就可以正式体验 Seata 服务。
+如果你创建事务分组时指定的namespace和clusterName下没有对应的Seata-Server，那么创建事务分组会失败。
+Client 配置完成后启动应用就可以正式体验 Seata 服务。
Tips：
- 1.请确保client与server的注册处于同一个namespace，不然会找不到服务。
diff --git
a/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
b/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
index 6111ab0ac31..e70cecb1307 100644
---
a/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
+++
b/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.4/user/registry/namingserver.md
@@ -129,6 +129,7 @@ curl -X POST http://localhost:8081/api/v1/auth/login \
### 创建client端的事务分组->seata集群的映射关系
+先启动namingserver,随后,启动 Seata-Server
向一个namingserver节点发起创建事务分组映射关系的http请求（namingserver节点会自动同步给其它节点）
```shell
@@ -147,7 +148,7 @@ curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/
（其中namespace是client端配置的命名空间，vGroup是client端配置的事务分组，clusterName是需要映射到的server端的集群名称）
-随后,启动 Seata-Server 后，Client 配置完成后启动应用就可以正式体验 Seata 服务。
+随后Client 配置完成后启动应用就可以正式体验 Seata 服务。
Tips：
- 1.请确保client与server的注册处于同一个namespace，不然会找不到服务。
diff --git
a/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
b/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
index 6111ab0ac31..5b4b4845a1d 100644
---
a/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
+++
b/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/user/registry/namingserver.md
@@ -129,6 +129,8 @@ curl -X POST http://localhost:8081/api/v1/auth/login \
### 创建client端的事务分组->seata集群的映射关系
+先启动namingserver,随后,启动 Seata-Server
+
向一个namingserver节点发起创建事务分组映射关系的http请求（namingserver节点会自动同步给其它节点）
```shell
@@ -147,7 +149,8 @@ curl -X POST -H "authorization: Bearer xxxxxxx"
http://127.0.0.1:8081/naming/v1/
（其中namespace是client端配置的命名空间，vGroup是client端配置的事务分组，clusterName是需要映射到的server端的集群名称）
-随后,启动 Seata-Server 后，Client 配置完成后启动应用就可以正式体验 Seata 服务。
+如果你创建事务分组时指定的namespace和clusterName下没有对应的Seata-Server，那么创建事务分组会失败。
+Client 配置完成后启动应用就可以正式体验 Seata 服务。
Tips：
- 1.请确保client与server的注册处于同一个namespace，不然会找不到服务。
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
