This is an automated email from the ASF dual-hosted git repository.
davidzollo pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/seatunnel.git
The following commit(s) were added to refs/heads/dev by this push:
new 5fb34bc2e3 [Improve][Docs] Add minimum deployment config and clarify
backup-count N definition in Zeta separated cluster guide (#10854)
5fb34bc2e3 is described below
commit 5fb34bc2e3e0b14caeb1f2d2cfd484f31fd27510
Author: zhiwei.niu <[email protected]>
AuthorDate: Fri May 8 17:09:38 2026 +0800
[Improve][Docs] Add minimum deployment config and clarify backup-count N
definition in Zeta separated cluster guide (#10854)
---
.../engines/zeta/separated-cluster-deployment.md | 19 ++++++++++++++-
.../engines/zeta/separated-cluster-deployment.md | 27 ++++++++++++++++++----
2 files changed, 41 insertions(+), 5 deletions(-)
diff --git a/docs/en/engines/zeta/separated-cluster-deployment.md
b/docs/en/engines/zeta/separated-cluster-deployment.md
index 7d110578f9..e6575f381d 100644
--- a/docs/en/engines/zeta/separated-cluster-deployment.md
+++ b/docs/en/engines/zeta/separated-cluster-deployment.md
@@ -10,6 +10,23 @@ Among all the Master nodes, only one Master node works at
the same time, and the
This is the most recommended usage method. In this mode, the load on the
Master will be very low, and the Master has more resources for job scheduling,
task fault tolerance index monitoring, and providing RESTful API services,
etc., and will have higher stability. At the same time, the Worker node does
not store Imap data. All Imap data is stored on the Master node. Even if the
Worker node has a high load or crashes, it will not cause the Imap data to be
redistributed.
+## Minimum Deployment Configuration
+
+The following table lists the minimum and HA-recommended node counts for each
role in a separated cluster. Refer to the subsequent sections for detailed
parameter descriptions.
+
+**Node Requirements**
+
+| Role | Minimum Count | Recommended (HA) | Description |
+|------|---------------|------------------|-------------|
+| Master | 1 | 2 | Responsible for scheduling and IMap data storage. |
+| Worker | 1 | 2+ | Responsible for task execution. |
+
+:::tip
+
+A single Master node can start and run normally, but provides no high
availability. For HA, deploy at least 2 Master nodes: the default
`backup-count: 1` requires at least 2 Master nodes to place IMap backup
replicas. Without a second Master, a single Master failure will leave the
cluster unable to recover.
+
+:::
+
## 1. Download
[Download And Make SeaTunnel Installation Package](download-seatunnel.md)
@@ -71,7 +88,7 @@ SeaTunnel Engine implements cluster management based on
[Hazelcast IMDG](https:/
The `backup count` is a parameter that defines the number of synchronous
backups. For example, if it is set to 1, the backup of the partition will be
placed on one other member. If it is set to 2, it will be placed on two other
members.
-We recommend that the value of `backup-count` be `max(1, min(5, N/2))`. `N` is
the number of cluster nodes.
+We recommend that the value of `backup-count` be `max(1, min(5, N/2))`. `N` is
the number of Master nodes.
```yaml
seatunnel:
diff --git a/docs/zh/engines/zeta/separated-cluster-deployment.md
b/docs/zh/engines/zeta/separated-cluster-deployment.md
index bbc96c6834..05120db3e7 100644
--- a/docs/zh/engines/zeta/separated-cluster-deployment.md
+++ b/docs/zh/engines/zeta/separated-cluster-deployment.md
@@ -10,6 +10,25 @@ SeaTunnel Engine 的Master服务和Worker服务分离，每个服务单独一个
这是最推荐的一种使用方式，在该模式下Master的负载会很小，Master有更多的资源用来进行作业的调度，任务的容错指标监控以及提供rest
api服务等，会有更高的稳定性。同时Worker节点不存储Imap的数据，所有的Imap数据都存储在Master节点中，即使Worker节点负载高或者挂掉，也不会导致Imap数据重新分布。
+
+## 最小化部署配置
+
+以下列出分离集群各角色节点的最少数量与 HA 推荐数量，供初次部署规划参考。详细配置参数说明见后续各节。
+
+**节点要求**
+
+| 角色 | 最少数量 | 推荐（HA） | 说明 |
+|------|----------|------------|------|
+| Master | 1 | 2 | 负责调度与 IMap 数据存储 |
+| Worker | 1 | 2+ | 负责任务执行 |
+
+:::tip
+
+单个 Master 节点可以正常启动和运行，但不具备高可用能力。若需 HA，Master 至少部署 2 个：默认 `backup-count: 1`
要求至少 2 个 Master 节点才能存放 IMap 备份副本，否则单个 Master 宕机后集群将无法自愈。
+
+:::
+
+
## 1. 下载
[下载和制作SeaTunnel安装包](download-seatunnel.md)
@@ -75,7 +94,7 @@ SeaTunnel Engine 基于 [Hazelcast
IMDG](https://docs.hazelcast.com/imdg/4.1/)
`backup count` 是定义同步备份数量的参数。例如，如果设置为 1，则分区的备份将放置在一个其他成员上。如果设置为 2，则将放置在两个其他成员上。
-我们建议 `backup-count` 的值为 `max(1, min(5, N/2))`。 `N` 是集群节点的数量。
+我们建议 `backup-count` 的值为 `max(1, min(5, N/2))`。`N` 是 Master 节点的数量。
```yaml
seatunnel:
@@ -473,9 +492,9 @@ export SEATUNNEL_HOME=${seatunnel install path}
export PATH=$PATH:$SEATUNNEL_HOME/bin
```
-## 8. 提交作业和管理作业
+## 9. 提交作业和管理作业
-### 8.1 使用 SeaTunnel Engine 客户端提交作业
+### 9.1 使用 SeaTunnel Engine 客户端提交作业
#### 安装 SeaTunnel Engine 客户端
@@ -515,6 +534,6 @@ hazelcast-client:
现在集群部署完成了，您可以通过以下教程完成作业的提交和管理：[提交和管理作业](user-command.md)
-### 8.2 使用 REST API 提交作业
+### 9.2 使用 REST API 提交作业
SeaTunnel Engine 提供了 REST API 用于提交作业。有关详细信息，请参阅 [REST API V2](rest-api-v2.md)
\ No newline at end of file
