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 5e3939115a7 fix: correct port 7091 to 8091 in Raft deployment
documentation (#1047)
5e3939115a7 is described below
commit 5e3939115a71ace7afbdc2807ea2cacbe313298b
Author: lokidundun <[email protected]>
AuthorDate: Sat Dec 6 21:01:00 2025 +0800
fix: correct port 7091 to 8091 in Raft deployment documentation (#1047)
---
.../current/ops/deploy-server-raft.md | 8 ++++----
.../version-v2.5/ops/deploy-server-raft.md | 8 ++++----
.../current/ops/deploy-server-raft.md | 8 ++++----
.../version-v2.5/ops/deploy-server-raft.md | 8 ++++----
4 files changed, 16 insertions(+), 16 deletions(-)
diff --git
a/i18n/en/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
b/i18n/en/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
index 0d0c81f6ad3..9a95c3be948 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
+++ b/i18n/en/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
@@ -10,7 +10,7 @@ Seata-Raft mode is a transaction storage mode that integrates
storage and comput
Note: Since this mode does not support integration with third-party registry
centers, only one TC cluster is allowed for the entire chain, which means that
the TC cluster corresponding to the client's transaction group must remain
consistent. In the future, the Seata community will launch a self-contained
NamingServer that is compatible with the Seata-Raft mode and supports
multi-raft.
## Server
-1. Download the server application from
[RELEASE](https://github.com/apache/incubator-seata/releases) and unzip.
+1. Download the server application from
[RELEASE](https://github.com/apache/incubator-seata/releases) and unzip.
2. Change config
Add the following parameters under seata: in the application.yml file in the
conf.
@@ -62,7 +62,7 @@ bin\seata-server.bat
4. Volume expansion and contraction
-Assuming the original cluster list is "192.168.0.111:7091, 192.168.0.112:7091,
192.168.0.113:7091", whether it is scaling or shrinking, only need to modify
this string and submit it to the volume expansion and contraction interface of
a member, such as scaling "curl -X POST -i
http://192.168.0.111:7091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:
7091, 192.168.0.112:7091, 192.168.0.113:7091, 192.168.0.114:7091" ', if it is
scaling, only need to remove the nodes in the cluster [...]
+Assuming the original cluster list is "192.168.0.111:8091, 192.168.0.112:8091,
192.168.0.113:8091", whether it is scaling or shrinking, only need to modify
this string and submit it to the volume expansion and contraction interface of
a member, such as scaling "curl -X POST -i
http://192.168.0.111:8091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:
8091, 192.168.0.112:8091, 192.168.0.113:8091, 192.168.0.114:8091" ', if it is
scaling, only need to remove the nodes in the cluster [...]
Note: The seata.server.raft.server-addr configuration is invalid as long as
the cluster is built. Please perform volume expansion and contraction through
the API. The subsequent console will also integrate volume expansion and
contraction and cluster management functions.
## Client
@@ -72,7 +72,7 @@ Note: The seata.server.raft.server-addr configuration is
invalid as long as the
registry:
type: raft
raft:
- server-addr: 192.168.0.111:7091, 192.168.0.112:7091,
192.168.0.113:7091
+ server-addr: 192.168.0.111:8091, 192.168.0.112:8091,
192.168.0.113:8091
```
2. Change the TC cluster corresponding to the transaction group to the Raft
group of the server.
```
@@ -81,4 +81,4 @@ seata:
service:
vgroup-mapping:
default_tx_group: If server.raft.group is set to "default", then this
field should be set to "default" as well.
-```
\ No newline at end of file
+```
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
b/i18n/en/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
index 0d0c81f6ad3..9a95c3be948 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
@@ -10,7 +10,7 @@ Seata-Raft mode is a transaction storage mode that integrates
storage and comput
Note: Since this mode does not support integration with third-party registry
centers, only one TC cluster is allowed for the entire chain, which means that
the TC cluster corresponding to the client's transaction group must remain
consistent. In the future, the Seata community will launch a self-contained
NamingServer that is compatible with the Seata-Raft mode and supports
multi-raft.
## Server
-1. Download the server application from
[RELEASE](https://github.com/apache/incubator-seata/releases) and unzip.
+1. Download the server application from
[RELEASE](https://github.com/apache/incubator-seata/releases) and unzip.
2. Change config
Add the following parameters under seata: in the application.yml file in the
conf.
@@ -62,7 +62,7 @@ bin\seata-server.bat
4. Volume expansion and contraction
-Assuming the original cluster list is "192.168.0.111:7091, 192.168.0.112:7091,
192.168.0.113:7091", whether it is scaling or shrinking, only need to modify
this string and submit it to the volume expansion and contraction interface of
a member, such as scaling "curl -X POST -i
http://192.168.0.111:7091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:
7091, 192.168.0.112:7091, 192.168.0.113:7091, 192.168.0.114:7091" ', if it is
scaling, only need to remove the nodes in the cluster [...]
+Assuming the original cluster list is "192.168.0.111:8091, 192.168.0.112:8091,
192.168.0.113:8091", whether it is scaling or shrinking, only need to modify
this string and submit it to the volume expansion and contraction interface of
a member, such as scaling "curl -X POST -i
http://192.168.0.111:8091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:
8091, 192.168.0.112:8091, 192.168.0.113:8091, 192.168.0.114:8091" ', if it is
scaling, only need to remove the nodes in the cluster [...]
Note: The seata.server.raft.server-addr configuration is invalid as long as
the cluster is built. Please perform volume expansion and contraction through
the API. The subsequent console will also integrate volume expansion and
contraction and cluster management functions.
## Client
@@ -72,7 +72,7 @@ Note: The seata.server.raft.server-addr configuration is
invalid as long as the
registry:
type: raft
raft:
- server-addr: 192.168.0.111:7091, 192.168.0.112:7091,
192.168.0.113:7091
+ server-addr: 192.168.0.111:8091, 192.168.0.112:8091,
192.168.0.113:8091
```
2. Change the TC cluster corresponding to the transaction group to the Raft
group of the server.
```
@@ -81,4 +81,4 @@ seata:
service:
vgroup-mapping:
default_tx_group: If server.raft.group is set to "default", then this
field should be set to "default" as well.
-```
\ No newline at end of file
+```
diff --git
a/i18n/zh-cn/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
b/i18n/zh-cn/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
index 70950f5d812..6f1010956f6 100644
---
a/i18n/zh-cn/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
+++
b/i18n/zh-cn/docusaurus-plugin-content-docs/current/ops/deploy-server-raft.md
@@ -9,7 +9,7 @@ Seata-Raft模式为存算一体的高性能易扩展，入门门槛低，运维
注：由于此模式不支持与第三方注册中心搭配，故全链路只允许存在一个tc集群，也就是客户端的事务分组对应的tc集群要保持一致。后续Seata社区将会推出自闭环的NamingServer，将于Seata-Raft模式对接，支持multi-raft。
## Server
-1. 在[RELEASE](https://github.com/apache/incubator-seata/releases)页面下载相应版本并解压
+1. 在[RELEASE](https://github.com/apache/incubator-seata/releases)页面下载相应版本并解压
2. 修改配置
将conf中application.yml编辑，在`seata:`下增加以下参数
@@ -61,7 +61,7 @@ bin\seata-server.bat
4. 扩缩容方式
-假设原集群列表为`192.168.0.111:7091,192.168.0.112:7091,192.168.0.113:7091`，无论是扩容还是缩容，只需要对这个字符串进行修改，并提交到一个所在成员的扩缩容接口即可，比如扩容`curl
-X POST -i
http://192.168.0.111:7091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:7091,192.168.0.112:7091,192.168.0.113:7091,192.168.0.114:7091"`，如果是缩容，只需要将集群连接串中需要下线的节点进行去除，并调用扩缩容接口即可.
+假设原集群列表为`192.168.0.111:8091,192.168.0.112:8091,192.168.0.113:8091`，无论是扩容还是缩容，只需要对这个字符串进行修改，并提交到一个所在成员的扩缩容接口即可，比如扩容`curl
-X POST -i
http://192.168.0.111:8091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:8091,192.168.0.112:8091,192.168.0.113:8091,192.168.0.114:8091"`，如果是缩容，只需要将集群连接串中需要下线的节点进行去除，并调用扩缩容接口即可.
注：seata.server.raft.server-addr配置只要集群构建完成后，修改该配置就无效了，请统一通过api方式进行扩缩容，后续控制台中也会集成扩缩容和集群管理功能。
## Client
@@ -71,7 +71,7 @@ bin\seata-server.bat
registry:
type: raft
raft:
- server-addr: 192.168.0.111:7091, 192.168.0.112:7091,
192.168.0.113:7091
+ server-addr: 192.168.0.111:8091, 192.168.0.112:8091,
192.168.0.113:8091
```
2. 将事务分组对应的tc集群改为server的raft group
```
@@ -80,4 +80,4 @@ seata:
service:
vgroup-mapping:
default_tx_group: 如果server.raft.group为default，那么此处便是default
-```
\ No newline at end of file
+```
diff --git
a/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
b/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
index 70950f5d812..6f1010956f6 100644
---
a/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
+++
b/i18n/zh-cn/docusaurus-plugin-content-docs/version-v2.5/ops/deploy-server-raft.md
@@ -9,7 +9,7 @@ Seata-Raft模式为存算一体的高性能易扩展，入门门槛低，运维
注：由于此模式不支持与第三方注册中心搭配，故全链路只允许存在一个tc集群，也就是客户端的事务分组对应的tc集群要保持一致。后续Seata社区将会推出自闭环的NamingServer，将于Seata-Raft模式对接，支持multi-raft。
## Server
-1. 在[RELEASE](https://github.com/apache/incubator-seata/releases)页面下载相应版本并解压
+1. 在[RELEASE](https://github.com/apache/incubator-seata/releases)页面下载相应版本并解压
2. 修改配置
将conf中application.yml编辑，在`seata:`下增加以下参数
@@ -61,7 +61,7 @@ bin\seata-server.bat
4. 扩缩容方式
-假设原集群列表为`192.168.0.111:7091,192.168.0.112:7091,192.168.0.113:7091`，无论是扩容还是缩容，只需要对这个字符串进行修改，并提交到一个所在成员的扩缩容接口即可，比如扩容`curl
-X POST -i
http://192.168.0.111:7091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:7091,192.168.0.112:7091,192.168.0.113:7091,192.168.0.114:7091"`，如果是缩容，只需要将集群连接串中需要下线的节点进行去除，并调用扩缩容接口即可.
+假设原集群列表为`192.168.0.111:8091,192.168.0.112:8091,192.168.0.113:8091`，无论是扩容还是缩容，只需要对这个字符串进行修改，并提交到一个所在成员的扩缩容接口即可，比如扩容`curl
-X POST -i
http://192.168.0.111:8091/metadata/v1/changeCluster?raftClusterStr=192.168.0.111:8091,192.168.0.112:8091,192.168.0.113:8091,192.168.0.114:8091"`，如果是缩容，只需要将集群连接串中需要下线的节点进行去除，并调用扩缩容接口即可.
注：seata.server.raft.server-addr配置只要集群构建完成后，修改该配置就无效了，请统一通过api方式进行扩缩容，后续控制台中也会集成扩缩容和集群管理功能。
## Client
@@ -71,7 +71,7 @@ bin\seata-server.bat
registry:
type: raft
raft:
- server-addr: 192.168.0.111:7091, 192.168.0.112:7091,
192.168.0.113:7091
+ server-addr: 192.168.0.111:8091, 192.168.0.112:8091,
192.168.0.113:8091
```
2. 将事务分组对应的tc集群改为server的raft group
```
@@ -80,4 +80,4 @@ seata:
service:
vgroup-mapping:
default_tx_group: 如果server.raft.group为default，那么此处便是default
-```
\ No newline at end of file
+```
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
