diff --git a/docs/getting-started/install-and-setup/install-enterprise-edition.md b/docs/getting-started/install-and-setup/install-enterprise-edition.md
index d2a4d2de..9033b39d 100644
--- a/docs/getting-started/install-and-setup/install-enterprise-edition.md
+++ b/docs/getting-started/install-and-setup/install-enterprise-edition.md
@@ -1,6 +1,6 @@
# Deploy TapData Enterprise
-The Enterprise Edition supports both single-node and high-availability deployments. This article explains how to quickly deploy it locally on Linux and Windows platforms (single-node architecture). For production environments, it is recommended to use the [high-availability deployment](../../platform-ops/production-deploy/install-tapdata-ha.md) approach.
+The Enterprise Edition supports both single-node and high-availability deployments. This article explains how to quickly deploy it locally on Linux and Windows platforms (single-node architecture). For production environments, it is recommended to use the [high-availability deployment](../../platform-ops/production-deploy/install-tapdata-ha-with-3-node.md) approach.
```mdx-code-block
import Tabs from '@theme/Tabs';
diff --git a/docs/images/tapdata_ha_with_3_node.png b/docs/images/tapdata_ha_with_3_node.png
index 6b1d0504..69df9ad7 100644
Binary files a/docs/images/tapdata_ha_with_3_node.png and b/docs/images/tapdata_ha_with_3_node.png differ
diff --git a/docs/introduction/compare-editions.md b/docs/introduction/compare-editions.md
index 938e28c8..2efeddfb 100644
--- a/docs/introduction/compare-editions.md
+++ b/docs/introduction/compare-editions.md
@@ -92,7 +92,7 @@ Building on the free offerings of TapData Community for developers, TapData Ente
| Local |
- | Horizontal Scaling of Processing Engine |
+ Horizontal Scaling of Processing Engine |
✅ |
✅ |
➖ |
diff --git a/docs/platform-ops/emergency-plan.md b/docs/platform-ops/emergency-plan.md
index 6cdad01f..e4b2cc93 100644
--- a/docs/platform-ops/emergency-plan.md
+++ b/docs/platform-ops/emergency-plan.md
@@ -4,7 +4,7 @@ This document provides a comprehensive emergency handling process and contingenc
:::tip
-TapData supports both standalone and high-availability deployments. For production environments, it is recommended to use a [high-availability deployment](production-deploy/install-tapdata-ha.md) method.
+TapData supports both standalone and high-availability deployments. For production environments, it is recommended to use a [high-availability deployment](production-deploy/install-tapdata-ha-with-3-node.md) method.
:::
@@ -39,7 +39,7 @@ Facing engine service exceptions, our goal is to minimize business impact and qu
#### High-Availability (HA) Deployment
-In a [high-availability environment](production-deploy/install-tapdata-ha.md), tasks from a single exceptional engine are expected to be gradually taken over by other engines within 10 minutes to minimize task impact, while attempts to automatically recover the exceptional engine will be made in the background.
+In a [high-availability environment](production-deploy/install-tapdata-ha-with-3-node.md), tasks from a single exceptional engine are expected to be gradually taken over by other engines within 10 minutes to minimize task impact, while attempts to automatically recover the exceptional engine will be made in the background.
#### Single Engine Deployment
@@ -58,7 +58,7 @@ Facing management end exceptions, our goal is to ensure business continuity and
#### High-Availability (HA) Deployment
-In a [high-availability environment](production-deploy/install-tapdata-ha.md), as long as at least one management end is running normally, all tasks will continue to run unaffected. If all management ends are exceptional, the recovery strategy is the same as for a single management end deployment.
+In a [high-availability environment](production-deploy/install-tapdata-ha-with-3-node.md), as long as at least one management end is running normally, all tasks will continue to run unaffected. If all management ends are exceptional, the recovery strategy is the same as for a single management end deployment.
#### Single Management End Deployment
diff --git a/docs/platform-ops/operation.md b/docs/platform-ops/operation.md
index 3590e487..6ec20d50 100644
--- a/docs/platform-ops/operation.md
+++ b/docs/platform-ops/operation.md
@@ -225,7 +225,7 @@ If the memory allocation is small but the task load is heavy, the Java program m
## How Does TapData Achieve High Availability?
-You can [deploy TapData on multiple machines](production-deploy/install-tapdata-ha.md) to achieve high availability. If one node experiences an anomaly, other nodes can continue to provide services. Tasks that have entered the incremental phase will resume from the breakpoint, and tasks can be automatically balanced and distributed.
+You can [deploy TapData on multiple machines](production-deploy/install-tapdata-ha-with-3-node.md) to achieve high availability. If one node experiences an anomaly, other nodes can continue to provide services. Tasks that have entered the incremental phase will resume from the breakpoint, and tasks can be automatically balanced and distributed.
## A Task Encounters an Exception, How to Troubleshoot?
diff --git a/docs/platform-ops/production-deploy/capacity-planning.md b/docs/platform-ops/production-deploy/capacity-planning.md
index 87eaaee6..175dfdd4 100644
--- a/docs/platform-ops/production-deploy/capacity-planning.md
+++ b/docs/platform-ops/production-deploy/capacity-planning.md
@@ -66,7 +66,7 @@ This document provides a comprehensive capacity planning reference to help users
## High Availability Configuration Recommendations
-In [High Availability (HA) deployment](install-tapdata-ha.md) scenarios, at least two TapData instances are typically deployed to ensure failover and business continuity. During failover, all pipelines from one instance will automatically transfer to the other instance. In this case, the remaining instance will bear additional load. To avoid excessive load, it is recommended to configure the number of pipelines at 50% ~ 75% of the server capacity to maintain the necessary performance buffer.
+In [High Availability (HA) deployment](install-tapdata-ha-with-3-node.md) scenarios, at least two TapData instances are typically deployed to ensure failover and business continuity. During failover, all pipelines from one instance will automatically transfer to the other instance. In this case, the remaining instance will bear additional load. To avoid excessive load, it is recommended to configure the number of pipelines at 50% ~ 75% of the server capacity to maintain the necessary performance buffer.
For example, if a 16-core server is configured to run 16 pipelines, in an HA setup, it is advisable to run only 8 ~ 12 pipelines to ensure system stability and high availability.
diff --git a/docs/platform-ops/production-deploy/install-replica-mongodb.md b/docs/platform-ops/production-deploy/install-replica-mongodb.md
index 9d9a7510..1d71bc99 100644
--- a/docs/platform-ops/production-deploy/install-replica-mongodb.md
+++ b/docs/platform-ops/production-deploy/install-replica-mongodb.md
@@ -165,7 +165,7 @@ We recommend using MongoDB version 4.0 or higher. This example uses CentOS 7 to
## Next Steps
-[Deploying High-Availability TapData](install-tapdata-ha.md)
+[Deploying High-Availability TapData](install-tapdata-ha-with-3-node.md)
## See Also
diff --git a/sidebars.js b/sidebars.js
index 6be7a1c6..101ecc52 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -406,7 +406,6 @@ const sidebars = {
link: {type: 'doc', id: 'platform-ops/production-deploy/README'},
items:[
'platform-ops/production-deploy/capacity-planning',
- 'platform-ops/production-deploy/install-tapdata-ha',
'platform-ops/production-deploy/install-tapdata-ha-with-3-node',
'platform-ops/production-deploy/disaster-recovery',
'platform-ops/production-deploy/install-replica-mongodb',