vesoft-inc · cooper-lzy · Aug 11, 2023 · May 19, 2023 · May 19, 2023 · May 19, 2023
diff --git a/.gitignore b/.gitignore
@@ -1,4 +1,3 @@
 site/
 *.DS_Store
 *.diff
-
diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
@@ -110,7 +110,7 @@ Graphs consist of vertices and edges. NebulaGraph uses key-value pairs to store
 
 NebulaGraph uses strong-typed Schema.
 
-NebulaGraph will store the properties of vertex and edges in order after encoding them. Since the length of properties is fixed, queries can be made in no time according to offset. Before decoding, NebulaGraph needs to get (and cache) the schema information in the Meta Service. In addition, when encoding properties, NebulaGraph will add the corresponding schema version to support online schema change.
+NebulaGraph will store the properties of vertex and edges in order after encoding them. Since the length of fixed-length properties is fixed, queries can be made in no time according to offset. Before decoding, NebulaGraph needs to get (and cache) the schema information in the Meta Service. In addition, when encoding properties, NebulaGraph will add the corresponding schema version to support online schema change.
 
 ## Data partitioning
 

diff --git a/docs-2.0/14.client/6.nebula-go-client.md b/docs-2.0/14.client/6.nebula-go-client.md
@@ -38,10 +38,10 @@ The NebulaGraph GO client provides both Connection Pool and Session Pool, using
 
 - Session Pool  
 
-  For details about all the code, see [session_pool_example.go](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/session_pool_example/session_pool_example.go).
+  For details about all the code, see [session_pool_example.go](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/examples/session_pool_example/session_pool_example.go).
 
   For limitations of using Session Pool, see [Usage example](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/README.md#usage-example).
 
 - Connection Pool
 
-  For all the code, see [graph_client_basic_example](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/basic_example/graph_client_basic_example.go) and [graph_client_goroutines_example](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/gorountines_example/graph_client_goroutines_example.go).
+  For all the code, see [graph_client_basic_example](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/examples/basic_example/graph_client_basic_example.go) and [graph_client_goroutines_example](https://github.com/vesoft-inc/nebula-go/blob/{{go.branch}}/examples/gorountines_example/graph_client_goroutines_example.go).
diff --git a/docs-2.0/2.quick-start/1.quick-start-workflow.md b/docs-2.0/2.quick-start/1.quick-start-workflow.md
diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md
@@ -35,6 +35,16 @@ NebulaGraph is still under development. Its behavior changes from time to time.
 
 ## About execution errors
 
+### "How to resolve the error `-1005:GraphMemoryExceeded: (-2600)`?"
+
+This error is issued by the Memory Tracker when it observes that memory usage has exceeded a set threshold. This mechanism can help avoid service processes from being terminated by the system's OOM (Out of Memory) killer. Steps to resolve:
+
+1. Check memory usage: First, you need to check the memory usage during the execution of the command. If the memory usage is indeed high, then this error might be expected.
+
+2. Check the configuration of the Memory Tracker: If the memory usage is not high, check the relevant configurations of the Memory Tracker. These include `memory_tracker_untracked_reserved_memory_mb` (untracked reserved memory in MB), `memory_tracker_limit_ratio` (memory limit ratio), and `memory_purge_enabled` (whether memory purge is enabled). For the configuration of the Memory Tracker, see [memory tracker configuration](../5.configurations-and-logs/1.configurations/4.storage-config.md#memory_tracker_configurations).
+
+3. Optimize configurations: Adjust these configurations according to the actual situation. For example, if the available memory limit is too low, you can increase the value of `memory_tracker_limit_ratio`.
+
 ### "How to resolve the error `SemanticError: Missing yield clause.`?"
 
 Starting with NebulaGraph 3.0.0, the statements `LOOKUP`, `GO`, and `FETCH` must output results with the `YIELD` clause. For more information, see [YIELD](../3.ngql-guide/8.clauses-and-options/yield.md).
@@ -555,40 +565,7 @@ If you have not modified the predefined ports in the [Configurations](../5.confi
 
 If you have customized the configuration files and changed the predefined ports, find the port numbers in your configuration files and open them on the firewalls.
 
-For those eco-tools, see the corresponding document.
-
-The following are the default ports used by NebulaGraph core and peripheral tools.
-
-| No. | Product / Service          | Type | Default                      | Description                                                    |
-| :--- | :--------------------- | :--- | :---------------------------- | :----------------------------------------------------------- |
-| 1    | NebulaGraph            | TCP  | 9669                          | Graph service RPC daemon listening port (commonly used for client connections to the Graph service). |
-| 2    | NebulaGraph            | TCP  | 19669                         | Graph service HTTP port.                                     |
-| 3    | NebulaGraph            | TCP  | 19670                         | Graph service HTTP/2 port. (Deprecated after version 3.x)                    |
-| 4    | NebulaGraph            | TCP  | 9559                          | Meta service RPC daemon listening port. (Commonly used by Graph and Storage services for querying and updating metadata in the graph database). |
-| 5    | NebulaGraph            | TCP  | 9560                          | Raft communication port between Meta services.                              |
-| 6    | NebulaGraph            | TCP  | 19559                         | Meta service HTTP port.                                      |
-| 7    | NebulaGraph            | TCP  | 19560                         | Meta service HTTP/2 port. (Deprecated after version 3.x)                     |
-| 8    | NebulaGraph            | TCP  | 9777                          | Drainer service port in Storage services (exposed only in Enterprise Edition clusters). |
-| 9    | NebulaGraph            | TCP  | 9778                          | Admin service port in Storage services.                         |
-| 10   | NebulaGraph            | TCP  | 9779                          | Storage service RPC daemon listening port. (Commonly used by Graph services for data storage-related operations, such as reading, writing, or deleting data). |
-| 11   | NebulaGraph            | TCP  | 9780                          | Raft communication port between Storage services.                           |
-| 12   | NebulaGraph            | TCP  | 19779                         | Storage service HTTP port.                                   |
-| 13   | NebulaGraph            | TCP  | 19780                         | Storage service HTTP/2 port. (Deprecated after version 3.x)                  |
-| 14   | NebulaGraph            | TCP  | 8888                          | Backup and restore Agent service port. The Agent is a daemon running on each machine in the cluster, responsible for starting and stopping NebulaGraph services and uploading and downloading backup files. |
-| 15   | NebulaGraph            | TCP  | 9789, 9790, and 9788 | Full-text index Raft Listener port, which reads data from Storage services and writes it to the Elasticsearch cluster.<br/>Also the port for Storage Listener in inter-cluster data synchronization, used for synchronizing Storage data from the primary cluster. Ports 9790 and 9788 are generated by adding and subtracting one from port 9789. |
-| 16   | NebulaGraph            | TCP  | 9200                          | NebulaGraph uses this port for HTTP communication with Elasticsearch to perform full-text search queries and manage full-text indexes. |
-| 17   | NebulaGraph            | TCP  | 9569, 9570, and 9568| Meta Listener port in inter-cluster data synchronization, used for synchronizing Meta data from the primary cluster. Ports 9570 and 9568 are generated by adding and subtracting one from port 9569. |
-| 18   | NebulaGraph            | TCP  | 9889, 9890, and 9888 |Drainer service port in inter-cluster data synchronization, used for synchronizing Storage and Meta data to the primary cluster. Ports 9890 and 9888 are generated by adding and subtracting one from port 9889. |
-| 19 | NebulaGraph Studio | TCP | 7001 | Studio web service port. |
-| 20 | NebulaGraph Dashboard | TCP | 8090 | Nebula HTTP Gateway dependency service port. Provides an HTTP interface for cluster services to interact with the NebulaGraph database using nGQL statements. |
-| 21 | NebulaGraph Dashboard | TCP | 9200 | Nebula Stats Exporter dependency service port. Collects cluster performance metrics, including service IP addresses, versions, and monitoring metrics (such as query count, query latency, heartbeat latency, etc.). |
-| 22 | NebulaGraph Dashboard | TCP | 9100 | Node Exporter dependency service port. Collects resource information for machines in the cluster, including CPU, memory, load, disk, and traffic. |
-| 23 | NebulaGraph Dashboard | TCP | 9091 | Prometheus service port. Time-series database for storing monitoring data. |
-| 24 | NebulaGraph Dashboard | TCP | 7003 | Dashboard Community Edition web service port. |
-| 25 | NebulaGraph Dashboard | TCP | 7005 | Dashboard Enterprise Edition web service port. |
-| 26 | NebulaGraph Dashboard | TCP | 9093 | Alertmanager service port. Receives alerts from Prometheus and sends alert notifications to Dashboard. |
-| 27 | NebulaGraph Explorer | TCP | 7002 | Explorer web service port. |
-
+For more port information, see [Port Guide for Company Products](port-guide.md).
 
 ### "How to test whether a port is open or closed?"
 

diff --git a/docs-2.0/20.appendix/6.eco-tool-version.md b/docs-2.0/20.appendix/6.eco-tool-version.md
@@ -137,7 +137,7 @@ NebulaGraph Console is the native CLI client of NebulaGraph. For how to use it,
 
 ## NebulaGraph Docker Compose
 
-Docker Compose can quickly deploy NebulaGraph clusters. For how to use it, please refer to [Docker Compose Deployment NebulaGraph](../4.deployment-and-installation/2.compile-and-install-nebula-graph/3.deploy-nebula-graph-with-docker-compose.md ).
+Docker Compose can quickly deploy NebulaGraph clusters. For how to use it, please refer to [Docker Compose Deployment NebulaGraph](../2.quick-start/1.quick-start-workflow.md).
 
 |NebulaGraph version|Docker Compose version|
 |:---|:---|

diff --git a/docs-2.0/20.appendix/learning-path.md b/docs-2.0/20.appendix/learning-path.md
@@ -49,7 +49,7 @@ After completing the NebulaGraph learning path, taking [NebulaGraph Certificatio
   | ------------------------------------------------------------ | ------------------------------------------------------------ |
   | [Install with a RPM or DEB package](../4.deployment-and-installation/2.compile-and-install-nebula-graph/2.install-nebula-graph-by-rpm-or-deb.md) | -                                                            |
   | [Install with a TAR package](../4.deployment-and-installation/2.compile-and-install-nebula-graph/4.install-nebula-graph-from-tar.md) | -                                                            |
-  | [Install with Docker](../4.deployment-and-installation/2.compile-and-install-nebula-graph/3.deploy-nebula-graph-with-docker-compose.md) | [Install NebulaGraph with Docker and Docker Compose](https://www.youtube.com/watch?v=yM5GDpJedEI) |
+  | [Install with Docker](../2.quick-start/1.quick-start-workflow.md) | [Install NebulaGraph with Docker and Docker Compose](https://www.youtube.com/watch?v=yM5GDpJedEI) |
   | [Install from source](../4.deployment-and-installation/2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md) | [Install NebulaGraph with Source Code](https://www.youtube.com/watch?v=x-I835eEBz0)                                                             |
 
 

diff --git a/docs-2.0/20.appendix/port-guide.md b/docs-2.0/20.appendix/port-guide.md
@@ -0,0 +1,34 @@
+# Port guide for company products
+
+The following are the default ports used by NebulaGraph core and peripheral tools.
+
+| No. | Product / Service          | Type | Default                      | Description                                                    |
+| :--- | :--------------------- | :--- | :---------------------------- | :----------------------------------------------------------- |
+| 1    | NebulaGraph            | TCP  | 9669                          | Graph service RPC daemon listening port (commonly used for client connections to the Graph service). |
+| 2    | NebulaGraph            | TCP  | 19669                         | Graph service HTTP port.                                     |
+| 3    | NebulaGraph            | TCP  | 19670                         | Graph service HTTP/2 port. (Deprecated after version 3.x)                    |
+| 4    | NebulaGraph            | TCP  | 9559                          | Meta service RPC daemon listening port. (Commonly used by Graph and Storage services for querying and updating metadata in the graph database). |
+| 5    | NebulaGraph            | TCP  | 9560                          | Raft communication port between Meta services.                              |
+| 6    | NebulaGraph            | TCP  | 19559                         | Meta service HTTP port.                                      |
+| 7    | NebulaGraph            | TCP  | 19560                         | Meta service HTTP/2 port. (Deprecated after version 3.x)                     |
+| 8    | NebulaGraph            | TCP  | 9777                          | Drainer service port in Storage services (exposed only in Enterprise Edition clusters). |
+| 9    | NebulaGraph            | TCP  | 9778                          | Admin service port in Storage services.                         |
+| 10   | NebulaGraph            | TCP  | 9779                          | Storage service RPC daemon listening port. (Commonly used by Graph services for data storage-related operations, such as reading, writing, or deleting data). |
+| 11   | NebulaGraph            | TCP  | 9780                          | Raft communication port between Storage services.                           |
+| 12   | NebulaGraph            | TCP  | 19779                         | Storage service HTTP port.                                   |
+| 13   | NebulaGraph            | TCP  | 19780                         | Storage service HTTP/2 port. (Deprecated after version 3.x)                  |
+| 14   | NebulaGraph            | TCP  | 8888                          | Backup and restore Agent service port. The Agent is a daemon running on each machine in the cluster, responsible for starting and stopping NebulaGraph services and uploading and downloading backup files. |
+| 15   | NebulaGraph            | TCP  | 9789, 9790, and 9788 | Full-text index Raft Listener port, which reads data from Storage services and writes it to the Elasticsearch cluster.<br/>Also the port for Storage Listener in inter-cluster data synchronization, used for synchronizing Storage data from the primary cluster. Ports 9790 and 9788 are generated by adding and subtracting one from port 9789. |
+| 16   | NebulaGraph            | TCP  | 9200                          | NebulaGraph uses this port for HTTP communication with Elasticsearch to perform full-text search queries and manage full-text indexes. |
+| 17   | NebulaGraph            | TCP  | 9569, 9570, and 9568| Meta Listener port in inter-cluster data synchronization, used for synchronizing Meta data from the primary cluster. Ports 9570 and 9568 are generated by adding and subtracting one from port 9569. |
+| 18   | NebulaGraph            | TCP  | 9889, 9890, and 9888 |Drainer service port in inter-cluster data synchronization, used for synchronizing Storage and Meta data to the primary cluster. Ports 9890 and 9888 are generated by adding and subtracting one from port 9889. |
+| 19 | NebulaGraph Studio | TCP | 7001 | Studio web service port. |
+| 20 | NebulaGraph Dashboard | TCP | 8090 | Nebula HTTP Gateway dependency service port. Provides an HTTP interface for cluster services to interact with the NebulaGraph database using nGQL statements. |
+| 21 | NebulaGraph Dashboard | TCP | 9200 | Nebula Stats Exporter dependency service port. Collects cluster performance metrics, including service IP addresses, versions, and monitoring metrics (such as query count, query latency, heartbeat latency, etc.). |
+| 22 | NebulaGraph Dashboard | TCP | 9100 | Node Exporter dependency service port. Collects resource information for machines in the cluster, including CPU, memory, load, disk, and traffic. |
+| 23 | NebulaGraph Dashboard | TCP | 9091 | Prometheus service port. Time-series database for storing monitoring data. |
+| 24 | NebulaGraph Dashboard | TCP | 7003 | Dashboard Community Edition web service port. |
+| 25 | NebulaGraph Dashboard | TCP | 7005 | Dashboard Enterprise Edition web service port. |
+| 26 | NebulaGraph Dashboard | TCP | 9093 | Alertmanager service port. Receives alerts from Prometheus and sends alert notifications to Dashboard. |
+| 27 | NebulaGraph Explorer | TCP | 7002 | Explorer web service port. |
+| 28 | License Manager | TCP | 9119 | The port for the License Manager (LM) service. The LM service is used for managing licenses (only used in enterprise clusters).|
diff --git a/docs-2.0/20.appendix/release-notes/dashboard-ent-release-note.md b/docs-2.0/20.appendix/release-notes/dashboard-ent-release-note.md
@@ -7,7 +7,7 @@
   - Support deploying License Manager (LM) through Dashboard. For more detail, see [Activate Dashboard](../../nebula-dashboard-ent/3.connect-dashboard.md).
   - [Back up and restore](../../nebula-dashboard-ent/4.cluster-operator/operator/backup-and-restore.md) support full backup to local.
   - Add [Slow query analyst](../../nebula-dashboard-ent/4.cluster-operator/analysis-diagnosis/slow-query-analyst.md) function.
-  - The [Cluster diagnostics](../../nebula-dashboard-ent/4.cluster-operator/cluster-information/cluster-diagnosis.md) formula supports configuration.
+  - The [Cluster diagnostics](../../nebula-dashboard-ent/4.cluster-operator/analysis-diagnosis/cluster-diagnosis.md) formula supports configuration.
   - [Config Management](../../nebula-dashboard-ent/4.cluster-operator/operator/config-management.md) support **Add Config**, view the **Effective value** of the current configuration, and **View inconsistent configurations**.
   - In the [Notification endpoint](../../nebula-dashboard-ent/system-settings/notification-endpoint.md), the webhook supports configuring the **Webhook request body**.
   - Support [custom monitoring panel](../../nebula-dashboard-ent/4.cluster-operator/2.monitor.md).

diff --git a/docs-2.0/20.appendix/release-notes/explorer-release-note.md b/docs-2.0/20.appendix/release-notes/explorer-release-note.md
@@ -1,5 +1,13 @@
 # NebulaGraph Explorer release notes
 
+## v3.5.1
+
+- Bugfix
+
+  - Fix wrong links.
+  - Fix wrong text.
+  - Remove deprecated tool components.
+
 ## v3.5.0
 
 - Feature