diff --git a/src/.vuepress/sidebar/V2.0.x/en-Table.ts b/src/.vuepress/sidebar/V2.0.x/en-Table.ts index 01628f1c2..d9f84fb03 100644 --- a/src/.vuepress/sidebar/V2.0.x/en-Table.ts +++ b/src/.vuepress/sidebar/V2.0.x/en-Table.ts @@ -77,22 +77,16 @@ export const enSidebar = { collapsible: true, prefix: 'Basic-Concept/', children: [ + { text: 'Database Management', link: 'Database-Management' }, + { text: 'Table Management', link: 'Table-Management' }, + { text: 'Write&Updata Data', link: 'Write-Updata-Data' }, + { text: 'Query Data', link: 'Query-Data' }, { - text: 'Data Modeling', + text: 'Delete Data', collapsible: true, children: [ - { text: 'Database Management', link: 'Database-Management' }, - { text: 'Table Management', link: 'Table-Management' }, - { text: 'Write&Updata Data', link: 'Write-Updata-Data' }, - { text: 'Query Data', link: 'Query-Data' }, - { - text: 'Delete Data', - collapsible: true, - children: [ - { text: 'Delete Data', link: 'Delete-Data' }, - { text: 'TTL Delete Data', link: 'TTL-Delete-Data' }, - ], - }, + { text: 'Delete Data', link: 'Delete-Data' }, + { text: 'TTL Delete Data', link: 'TTL-Delete-Data' }, ], }, ], diff --git a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts index aaf461cb9..5a78de0fd 100644 --- a/src/.vuepress/sidebar/V2.0.x/en-Tree.ts +++ b/src/.vuepress/sidebar/V2.0.x/en-Tree.ts @@ -57,6 +57,7 @@ export const enSidebar = { collapsible: true, prefix: 'Deployment-and-Maintenance/', children: [ + { text: 'Deployment form', link: 'Deployment-form_apache' }, { text: 'Obtain IoTDB', link: 'IoTDB-Package_apache' }, { text: 'Database Resources', link: 'Database-Resources' }, { text: 'Environment Requirements', link: 'Environment-Requirements' }, @@ -76,13 +77,7 @@ export const enSidebar = { children: [ { text: 'Data Modeling', - collapsible: true, - children: [ - { - text: 'Measurement Point Management', - link: 'Operate-Metadata_apache', - }, - ], + link: 'Operate-Metadata_apache', }, { text: 'Write & Delete', link: 'Write-Delete-Data' }, { text: 'Query Data', link: 'Query-Data' }, diff --git a/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts b/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts index bc59d5448..be9bd2160 100644 --- a/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts +++ b/src/.vuepress/sidebar_timecho/V2.0.x/en-Table.ts @@ -77,22 +77,16 @@ export const enSidebar = { collapsible: true, prefix: 'Basic-Concept/', children: [ + { text: 'Database Management', link: 'Database-Management' }, + { text: 'Table Management', link: 'Table-Management' }, + { text: 'Write&Updata Data', link: 'Write-Updata-Data' }, + { text: 'Query Data', link: 'Query-Data' }, { - text: 'Data Modeling', + text: 'Delete Data', collapsible: true, children: [ - { text: 'Database Management', link: 'Database-Management' }, - { text: 'Table Management', link: 'Table-Management' }, - { text: 'Write&Updata Data', link: 'Write-Updata-Data' }, - { text: 'Query Data', link: 'Query-Data' }, - { - text: 'Delete Data', - collapsible: true, - children: [ - { text: 'Delete Data', link: 'Delete-Data' }, - { text: 'TTL Delete Data', link: 'TTL-Delete-Data' }, - ], - }, + { text: 'Delete Data', link: 'Delete-Data' }, + { text: 'TTL Delete Data', link: 'TTL-Delete-Data' }, ], }, ], diff --git a/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts b/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts index 0cfed6c30..16a9cbeb4 100644 --- a/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts +++ b/src/.vuepress/sidebar_timecho/V2.0.x/en-Tree.ts @@ -57,6 +57,7 @@ export const enSidebar = { collapsible: true, prefix: 'Deployment-and-Maintenance/', children: [ + { text: 'Deployment form', link: 'Deployment-form_timecho' }, { text: 'Obtain TimechoDB', link: 'IoTDB-Package_timecho' }, { text: 'Database Resources', link: 'Database-Resources' }, { text: 'Environment Requirements', link: 'Environment-Requirements' }, @@ -85,13 +86,7 @@ export const enSidebar = { children: [ { text: 'Data Modeling', - collapsible: true, - children: [ - { - text: 'Measurement Point Management', - link: 'Operate-Metadata_timecho', - }, - ], + link: 'Operate-Metadata_timecho', }, { text: 'Write & Delete', link: 'Write-Delete-Data' }, { text: 'Query Data', link: 'Query-Data' }, diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_apache.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_apache.md index 29ee83861..a934884cb 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_apache.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_apache.md @@ -18,7 +18,7 @@ under the License. --> -# Deployment-Mode_apache +# Deployment form IoTDB has two operation modes: standalone mode and cluster mode. diff --git a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_timecho.md b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_timecho.md index 90230e5c5..c757e9561 100644 --- a/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_timecho.md +++ b/src/UserGuide/Master/Table/Deployment-and-Maintenance/Deployment-form_timecho.md @@ -18,7 +18,7 @@ under the License. --> -# Deployment-Mode_apache +# Deployment form IoTDB has two operation modes: standalone mode and cluster mode. diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Deployment-form_apache.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Deployment-form_apache.md new file mode 100644 index 000000000..a934884cb --- /dev/null +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Deployment-form_apache.md @@ -0,0 +1,52 @@ + +# Deployment form + +IoTDB has two operation modes: standalone mode and cluster mode. + +## 1 Standalone Mode + +An IoTDB standalone instance includes 1 ConfigNode and 1 DataNode, referred to as 1C1D. + +- **Features**: Easy for developers to install and deploy, with lower deployment and maintenance costs, and convenient operation. +- **Applicable scenarios**: Situations with limited resources or where high availability is not a critical requirement, such as edge servers. +- **Deployment method**:[Stand-Alone Deployment](../Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md) + + +## 2 Cluster Mode + +An IoTDB cluster instance consists of 3 ConfigNodes and no fewer than 3 DataNodes, typically 3 DataNodes, referred to as 3C3D. In the event of partial node failures, the remaining nodes can still provide services, ensuring high availability of the database service, and the database performance can be improved with the addition of nodes. + +- **Features**: High availability and scalability, with the ability to enhance system performance by adding DataNodes. +- **Applicable scenarios**: Enterprise-level application scenarios that require high availability and reliability. +- **Deployment method**: [Cluster Deployment](../Deployment-and-Maintenance/Cluster-Deployment_apache.md) + +## 3 Summary of Features + +| **Dimension** | **Stand-Alone Mode** | **Cluster Mode** | +| :-------------------------- | :----------------------------------------------------- | :----------------------------------------------------------- | +| Applicable Scenario | Edge deployment, low requirement for high availability | High-availability business, disaster recovery scenarios, etc. | +| Number of Machines Required | 1 | ≥3 | +| Security and Reliability | Cannot tolerate single-point failure | High, can tolerate single-point failure | +| Scalability | Scalable by adding DataNodes to improve performance | Scalable by adding DataNodes to improve performance | +| Performance | Scalable with the number of DataNodes | Scalable with the number of DataNodes | + +- The deployment steps for standalone mode and cluster mode are similar (adding ConfigNodes and DataNodes one by one), with the only differences being the number of replicas and the minimum number of nodes required to provide services. \ No newline at end of file diff --git a/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Deployment-form_timecho.md b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Deployment-form_timecho.md new file mode 100644 index 000000000..c757e9561 --- /dev/null +++ b/src/UserGuide/Master/Tree/Deployment-and-Maintenance/Deployment-form_timecho.md @@ -0,0 +1,63 @@ + +# Deployment form + +IoTDB has two operation modes: standalone mode and cluster mode. + +## 1 Standalone Mode + +An IoTDB standalone instance includes 1 ConfigNode and 1 DataNode, i.e., 1C1D. + +- **Features**: Easy for developers to install and deploy, with low deployment and maintenance costs and convenient operations. +- **Use Cases**: Scenarios with limited resources or low high-availability requirements, such as edge servers. +- **Deployment Method**: [Stand-Alone Deployment](../Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md) + +## 2 Dual-Active Mode + +Dual-Active Deployment is a feature of TimechoDB, where two independent instances synchronize bidirectionally and can provide services simultaneously. If one instance stops and restarts, the other instance will resume data transfer from the breakpoint. + +> An IoTDB Dual-Active instance typically consists of 2 standalone nodes, i.e., 2 sets of 1C1D. Each instance can also be a cluster. + +- **Features**: The high-availability solution with the lowest resource consumption. +- **Use Cases**: Scenarios with limited resources (only two servers) but requiring high availability. +- **Deployment Method**: [Dual-Active Deployment](../Deployment-and-Maintenance/Dual-Active-Deployment_timecho.md) + +## 3 Cluster Mode + +An IoTDB cluster instance consists of 3 ConfigNodes and no fewer than 3 DataNodes, typically 3 DataNodes, i.e., 3C3D. If some nodes fail, the remaining nodes can still provide services, ensuring high availability of the database. Performance can be improved by adding DataNodes. + +- **Features**: High availability, high scalability, and improved system performance by adding DataNodes. +- **Use Cases**: Enterprise-level application scenarios requiring high availability and reliability. +- **Deployment Method**: [Cluster Deployment](../Deployment-and-Maintenance/Cluster-Deployment_timecho.md) + + + +## 4 Feature Summary + +| **Dimension** | **Stand-Alone Mode** | **Dual-Active Mode** | **Cluster Mode** | +| :-------------------------- | :------------------------------------------------------- | :------------------------------------------------------ | :------------------------------------------------------ | +| Use Cases | Edge-side deployment, low high-availability requirements | High-availability services, disaster recovery scenarios | High-availability services, disaster recovery scenarios | +| Number of Machines Required | 1 | 2 | ≥3 | +| Security and Reliability | Cannot tolerate single-point failure | High, can tolerate single-point failure | High, can tolerate single-point failure | +| Scalability | Can expand DataNodes to improve performance | Each instance can be scaled as needed | Can expand DataNodes to improve performance | +| Performance | Can scale with the number of DataNodes | Same as one of the instances | Can scale with the number of DataNodes | + +- The deployment steps for Stand-Alone Mode and Cluster Mode are similar (adding ConfigNodes and DataNodes one by one), with differences only in the number of replicas and the minimum number of nodes required to provide services. \ No newline at end of file diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_apache.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_apache.md index 29ee83861..a934884cb 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_apache.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_apache.md @@ -18,7 +18,7 @@ under the License. --> -# Deployment-Mode_apache +# Deployment form IoTDB has two operation modes: standalone mode and cluster mode. diff --git a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_timecho.md b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_timecho.md index 90230e5c5..c757e9561 100644 --- a/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_timecho.md +++ b/src/UserGuide/latest-Table/Deployment-and-Maintenance/Deployment-form_timecho.md @@ -18,7 +18,7 @@ under the License. --> -# Deployment-Mode_apache +# Deployment form IoTDB has two operation modes: standalone mode and cluster mode. diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Deployment-form_apache.md b/src/UserGuide/latest/Deployment-and-Maintenance/Deployment-form_apache.md new file mode 100644 index 000000000..a934884cb --- /dev/null +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Deployment-form_apache.md @@ -0,0 +1,52 @@ + +# Deployment form + +IoTDB has two operation modes: standalone mode and cluster mode. + +## 1 Standalone Mode + +An IoTDB standalone instance includes 1 ConfigNode and 1 DataNode, referred to as 1C1D. + +- **Features**: Easy for developers to install and deploy, with lower deployment and maintenance costs, and convenient operation. +- **Applicable scenarios**: Situations with limited resources or where high availability is not a critical requirement, such as edge servers. +- **Deployment method**:[Stand-Alone Deployment](../Deployment-and-Maintenance/Stand-Alone-Deployment_apache.md) + + +## 2 Cluster Mode + +An IoTDB cluster instance consists of 3 ConfigNodes and no fewer than 3 DataNodes, typically 3 DataNodes, referred to as 3C3D. In the event of partial node failures, the remaining nodes can still provide services, ensuring high availability of the database service, and the database performance can be improved with the addition of nodes. + +- **Features**: High availability and scalability, with the ability to enhance system performance by adding DataNodes. +- **Applicable scenarios**: Enterprise-level application scenarios that require high availability and reliability. +- **Deployment method**: [Cluster Deployment](../Deployment-and-Maintenance/Cluster-Deployment_apache.md) + +## 3 Summary of Features + +| **Dimension** | **Stand-Alone Mode** | **Cluster Mode** | +| :-------------------------- | :----------------------------------------------------- | :----------------------------------------------------------- | +| Applicable Scenario | Edge deployment, low requirement for high availability | High-availability business, disaster recovery scenarios, etc. | +| Number of Machines Required | 1 | ≥3 | +| Security and Reliability | Cannot tolerate single-point failure | High, can tolerate single-point failure | +| Scalability | Scalable by adding DataNodes to improve performance | Scalable by adding DataNodes to improve performance | +| Performance | Scalable with the number of DataNodes | Scalable with the number of DataNodes | + +- The deployment steps for standalone mode and cluster mode are similar (adding ConfigNodes and DataNodes one by one), with the only differences being the number of replicas and the minimum number of nodes required to provide services. \ No newline at end of file diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Deployment-form_timecho.md b/src/UserGuide/latest/Deployment-and-Maintenance/Deployment-form_timecho.md new file mode 100644 index 000000000..c757e9561 --- /dev/null +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Deployment-form_timecho.md @@ -0,0 +1,63 @@ + +# Deployment form + +IoTDB has two operation modes: standalone mode and cluster mode. + +## 1 Standalone Mode + +An IoTDB standalone instance includes 1 ConfigNode and 1 DataNode, i.e., 1C1D. + +- **Features**: Easy for developers to install and deploy, with low deployment and maintenance costs and convenient operations. +- **Use Cases**: Scenarios with limited resources or low high-availability requirements, such as edge servers. +- **Deployment Method**: [Stand-Alone Deployment](../Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md) + +## 2 Dual-Active Mode + +Dual-Active Deployment is a feature of TimechoDB, where two independent instances synchronize bidirectionally and can provide services simultaneously. If one instance stops and restarts, the other instance will resume data transfer from the breakpoint. + +> An IoTDB Dual-Active instance typically consists of 2 standalone nodes, i.e., 2 sets of 1C1D. Each instance can also be a cluster. + +- **Features**: The high-availability solution with the lowest resource consumption. +- **Use Cases**: Scenarios with limited resources (only two servers) but requiring high availability. +- **Deployment Method**: [Dual-Active Deployment](../Deployment-and-Maintenance/Dual-Active-Deployment_timecho.md) + +## 3 Cluster Mode + +An IoTDB cluster instance consists of 3 ConfigNodes and no fewer than 3 DataNodes, typically 3 DataNodes, i.e., 3C3D. If some nodes fail, the remaining nodes can still provide services, ensuring high availability of the database. Performance can be improved by adding DataNodes. + +- **Features**: High availability, high scalability, and improved system performance by adding DataNodes. +- **Use Cases**: Enterprise-level application scenarios requiring high availability and reliability. +- **Deployment Method**: [Cluster Deployment](../Deployment-and-Maintenance/Cluster-Deployment_timecho.md) + + + +## 4 Feature Summary + +| **Dimension** | **Stand-Alone Mode** | **Dual-Active Mode** | **Cluster Mode** | +| :-------------------------- | :------------------------------------------------------- | :------------------------------------------------------ | :------------------------------------------------------ | +| Use Cases | Edge-side deployment, low high-availability requirements | High-availability services, disaster recovery scenarios | High-availability services, disaster recovery scenarios | +| Number of Machines Required | 1 | 2 | ≥3 | +| Security and Reliability | Cannot tolerate single-point failure | High, can tolerate single-point failure | High, can tolerate single-point failure | +| Scalability | Can expand DataNodes to improve performance | Each instance can be scaled as needed | Can expand DataNodes to improve performance | +| Performance | Can scale with the number of DataNodes | Same as one of the instances | Can scale with the number of DataNodes | + +- The deployment steps for Stand-Alone Mode and Cluster Mode are similar (adding ConfigNodes and DataNodes one by one), with differences only in the number of replicas and the minimum number of nodes required to provide services. \ No newline at end of file