Skip to content

Commit

Permalink
Finish
Browse files Browse the repository at this point in the history
  • Loading branch information
@CRZbulabula
CRZbulabula committed Oct 18, 2023
1 parent 092d86a commit 27ed000
Show file tree
Hide file tree
Showing 21 changed files with 116 additions and 116 deletions.
18 changes: 9 additions & 9 deletions src/UserGuide/Master/Deployment-and-Maintenance/Deployment-Guide.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ For folder cluster1:
| cn\_internal\_address | 127.0.0.1 |
| cn\_internal\_port | 10711 |
| cn\_consensus\_port | 10721 |
| cn\_target\_config\_node\_list | 127.0.0.1:10710 |
| cn\_seed\_config\_node | 127.0.0.1:10710 |

+ Modify DataNode configurations:

Expand All @@ -150,7 +150,7 @@ For folder cluster1:
| dn\_mpp\_data\_exchange\_port | 10741 |
| dn\_schema\_region\_consensus\_port | 10751 |
| dn\_data\_region\_consensus\_port | 10761 |
| dn\_target\_config\_node\_list | 127.0.0.1:10710 |
| dn\_seed\_config\_node | 127.0.0.1:10710 |

For folder cluster2:

Expand All @@ -161,7 +161,7 @@ For folder cluster2:
| cn\_internal\_address | 127.0.0.1 |
| cn\_internal\_port | 10712 |
| cn\_consensus\_port | 10722 |
| cn\_target\_config\_node\_list | 127.0.0.1:10710 |
| cn\_seed\_config\_node | 127.0.0.1:10710 |

+ Modify DataNode configurations:

Expand All @@ -174,7 +174,7 @@ For folder cluster2:
| dn\_mpp\_data\_exchange\_port | 10742 |
| dn\_schema\_region\_consensus\_port | 10752 |
| dn\_data\_region\_consensus\_port | 10762 |
| dn\_target\_config\_node\_list | 127.0.0.1:10710 |
| dn\_seed\_config\_node | 127.0.0.1:10710 |

### 6. Expanding the Cluster

Expand Down Expand Up @@ -361,7 +361,7 @@ and set the following parameters based on the IP address and available port of t
| cn\_internal\_address | Internal rpc service address of ConfigNode | 127.0.0.1 | Set to the IPV4 address or domain name of the server |
| cn\_internal\_port | Internal rpc service port of ConfigNode | 10710 | Set to any unoccupied port |
| cn\_consensus\_port | ConfigNode replication consensus protocol communication port | 10720 | Set to any unoccupied port |
| cn\_target\_config\_node\_list | ConfigNode address to which the node is connected when it is registered to the cluster. Note that Only one ConfigNode can be configured. | 127.0.0.1:10710 | For Seed-ConfigNode, set to its own cn\_internal\_address:cn\_internal\_port; For other ConfigNodes, set to other one running ConfigNode's cn\_internal\_address:cn\_internal\_port |
| cn\_seed\_config\_node | ConfigNode address to which the node is connected when it is registered to the cluster. Note that Only one ConfigNode can be configured. | 127.0.0.1:10710 | For Seed-ConfigNode, set to its own cn\_internal\_address:cn\_internal\_port; For other ConfigNodes, set to other one running ConfigNode's cn\_internal\_address:cn\_internal\_port |

**Notice: The preceding configuration parameters cannot be changed after the node is started. Ensure that all ports are not occupied. Otherwise, the Node cannot be started.**

Expand All @@ -379,7 +379,7 @@ and set the following parameters based on the IP address and available port of t
| dn\_mpp\_data\_exchange\_port | Data flow port of DataNode inside cluster | 10740 | Set to any unoccupied port |
| dn\_data\_region\_consensus\_port | Data replicas communication port for consensus | 10750 | Set to any unoccupied port |
| dn\_schema\_region\_consensus\_port | Schema replicas communication port for consensus | 10760 | Set to any unoccupied port |
| dn\_target\_config\_node\_list | Running ConfigNode of the Cluster | 127.0.0.1:10710 | Set to any running ConfigNode's cn\_internal\_address:cn\_internal\_port. You can set multiple values, separate them with commas(",") |
| dn\_seed\_config\_node | Running ConfigNode of the Cluster | 127.0.0.1:10710 | Set to any running ConfigNode's cn\_internal\_address:cn\_internal\_port. You can set multiple values, separate them with commas(",") |

**Notice: The preceding configuration parameters cannot be changed after the node is started. Ensure that all ports are not occupied. Otherwise, the Node cannot be started.**

Expand Down Expand Up @@ -423,7 +423,7 @@ Then open its configuration file ./conf/iotdb-confignode.properties and check th
| cn\_internal\_address | Is set to the IPV4 address or domain name of the server |
| cn\_internal\_port | The port isn't occupied |
| cn\_consensus\_port | The port isn't occupied |
| cn\_target\_config\_node\_list | Is set to its own internal communication address, which is cn\_internal\_address:cn\_internal\_port |
| cn\_seed\_config\_node | Is set to its own internal communication address, which is cn\_internal\_address:cn\_internal\_port |

After checking, you can run the startup script on the server:

Expand Down Expand Up @@ -468,7 +468,7 @@ Then, please open its configuration file ./conf/iotdb-confignode.properties and
| cn\_internal\_address | Is set to the IPV4 address or domain name of the server |
| cn\_internal\_port | The port isn't occupied |
| cn\_consensus\_port | The port isn't occupied |
| cn\_target\_config\_node\_list | Is set to the internal communication address of an other running ConfigNode. The internal communication address of the seed ConfigNode is recommended. |
| cn\_seed\_config\_node | Is set to the internal communication address of an other running ConfigNode. The internal communication address of the seed ConfigNode is recommended. |

After checking, you can run the startup script on the server:

Expand Down Expand Up @@ -510,7 +510,7 @@ Then open its configuration file ./conf/iotdb-datanode.properties and check the
| dn\_mpp\_data\_exchange\_port | The port isn't occupied |
| dn\_data\_region\_consensus\_port | The port isn't occupied |
| dn\_schema\_region\_consensus\_port | The port isn't occupied |
| dn\_target\_config\_node\_list | Is set to the internal communication address of other running ConfigNodes. The internal communication address of the seed ConfigNode is recommended. |
| dn\_seed\_config\_node | Is set to the internal communication address of other running ConfigNodes. The internal communication address of the seed ConfigNode is recommended. |

After checking, you can run the startup script on the server:

Expand Down
10 changes: 5 additions & 5 deletions src/UserGuide/Master/Deployment-and-Maintenance/Deployment-Guide_timecho.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ and set the following parameters based on the IP address and available port of t
| cn\_internal\_address | Internal rpc service address of ConfigNode | 127.0.0.1 | Set to the IPV4 address or domain name of the server |
| cn\_internal\_port | Internal rpc service port of ConfigNode | 10710 | Set to any unoccupied port |
| cn\_consensus\_port | ConfigNode replication consensus protocol communication port | 10720 | Set to any unoccupied port |
| cn\_target\_config\_node\_list | ConfigNode address to which the node is connected when it is registered to the cluster. Note that Only one ConfigNode can be configured. | 127.0.0.1:10710 | For Seed-ConfigNode, set to its own cn\_internal\_address:cn\_internal\_port; For other ConfigNodes, set to other one running ConfigNode's cn\_internal\_address:cn\_internal\_port |
| cn\_seed\_config\_nod | ConfigNode address to which the node is connected when it is registered to the cluster. Note that Only one ConfigNode can be configured. | 127.0.0.1:10710 | For Seed-ConfigNode, set to its own cn\_internal\_address:cn\_internal\_port; For other ConfigNodes, set to other one running ConfigNode's cn\_internal\_address:cn\_internal\_port |

**Notice: The preceding configuration parameters cannot be changed after the node is started. Ensure that all ports are not occupied. Otherwise, the Node cannot be started.**

Expand All @@ -215,7 +215,7 @@ and set the following parameters based on the IP address and available port of t
| dn\_mpp\_data\_exchange\_port | Data flow port of DataNode inside cluster | 10740 | Set to any unoccupied port |
| dn\_data\_region\_consensus\_port | Data replicas communication port for consensus | 10750 | Set to any unoccupied port |
| dn\_schema\_region\_consensus\_port | Schema replicas communication port for consensus | 10760 | Set to any unoccupied port |
| dn\_target\_config\_node\_list | Running ConfigNode of the Cluster | 127.0.0.1:10710 | Set to any running ConfigNode's cn\_internal\_address:cn\_internal\_port. You can set multiple values, separate them with commas(",") |
| dn\_seed\_config\_node | Running ConfigNode of the Cluster | 127.0.0.1:10710 | Set to any running ConfigNode's cn\_internal\_address:cn\_internal\_port. You can set multiple values, separate them with commas(",") |

**Notice: The preceding configuration parameters cannot be changed after the node is started. Ensure that all ports are not occupied. Otherwise, the Node cannot be started.**

Expand Down Expand Up @@ -259,7 +259,7 @@ Then open its configuration file ./conf/iotdb-confignode.properties and check th
| cn\_internal\_address | Is set to the IPV4 address or domain name of the server |
| cn\_internal\_port | The port isn't occupied |
| cn\_consensus\_port | The port isn't occupied |
| cn\_target\_config\_node\_list | Is set to its own internal communication address, which is cn\_internal\_address:cn\_internal\_port |
| cn\_seed\_config\_node | Is set to its own internal communication address, which is cn\_internal\_address:cn\_internal\_port |

After checking, you can run the startup script on the server:

Expand Down Expand Up @@ -304,7 +304,7 @@ Then, please open its configuration file ./conf/iotdb-confignode.properties and
| cn\_internal\_address | Is set to the IPV4 address or domain name of the server |
| cn\_internal\_port | The port isn't occupied |
| cn\_consensus\_port | The port isn't occupied |
| cn\_target\_config\_node\_list | Is set to the internal communication address of an other running ConfigNode. The internal communication address of the seed ConfigNode is recommended. |
| cn\_seed\_config\_node | Is set to the internal communication address of an other running ConfigNode. The internal communication address of the seed ConfigNode is recommended. |

After checking, you can run the startup script on the server:

Expand Down Expand Up @@ -346,7 +346,7 @@ Then open its configuration file ./conf/iotdb-datanode.properties and check the
| dn\_mpp\_data\_exchange\_port | The port isn't occupied |
| dn\_data\_region\_consensus\_port | The port isn't occupied |
| dn\_schema\_region\_consensus\_port | The port isn't occupied |
| dn\_target\_config\_node\_list | Is set to the internal communication address of other running ConfigNodes. The internal communication address of the seed ConfigNode is recommended. |
| dn\_seed\_config\_node | Is set to the internal communication address of other running ConfigNodes. The internal communication address of the seed ConfigNode is recommended. |

After checking, you can run the startup script on the server:

Expand Down
14 changes: 7 additions & 7 deletions src/UserGuide/Master/Deployment-and-Maintenance/Docker-Install.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -38,12 +38,12 @@ docker run -d --name iotdb-service \
--ip 172.18.0.6 \
-p 6667:6667 \
-e cn_internal_address=iotdb-service \
-e cn_target_config_node_list=iotdb-service:10710 \
-e cn_seed_config_node=iotdb-service:10710 \
-e cn_internal_port=10710 \
-e cn_consensus_port=10720 \
-e dn_rpc_address=iotdb-service \
-e dn_internal_address=iotdb-service \
-e dn_target_config_node_list=iotdb-service:10710 \
-e dn_seed_config_node=iotdb-service:10710 \
-e dn_mpp_data_exchange_port=10740 \
-e dn_schema_region_consensus_port=10750 \
-e dn_data_region_consensus_port=10760 \
Expand Down Expand Up @@ -76,14 +76,14 @@ services:
- cn_internal_address=iotdb-service
- cn_internal_port=10710
- cn_consensus_port=10720
- cn_target_config_node_list=iotdb-service:10710
- cn_seed_config_node=iotdb-service:10710
- dn_rpc_address=iotdb-service
- dn_internal_address=iotdb-service
- dn_rpc_port=6667
- dn_mpp_data_exchange_port=10740
- dn_schema_region_consensus_port=10750
- dn_data_region_consensus_port=10760
- dn_target_config_node_list=iotdb-service:10710
- dn_seed_config_node=iotdb-service:10710
volumes:
- ./data:/iotdb/data
- ./logs:/iotdb/logs
Expand Down Expand Up @@ -112,7 +112,7 @@ services:
container_name: iotdb-confignode
environment:
- cn_internal_address=iotdb-2
- cn_target_config_node_list=iotdb-1:10710
- cn_seed_config_node=iotdb-1:10710
- cn_internal_port=10710
- cn_consensus_port=10720
- schema_replication_factor=3
Expand All @@ -132,7 +132,7 @@ services:
environment:
- dn_rpc_address=iotdb-2
- dn_internal_address=iotdb-2
- dn_target_config_node_list=iotdb-1:10710
- dn_seed_config_node=iotdb-1:10710
- data_replication_factor=3
- dn_rpc_port=6667
- dn_mpp_data_exchange_port=10740
Expand All @@ -151,7 +151,7 @@ services:
Notice：
1. The `dn_target_config_node_list` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
1. The `dn_seed_config_node` of three nodes must the same and it is the first starting node of `iotdb-1` with the cn_internal_port of 10710。
2. In this docker-compose file，`iotdb-2` should be replace with the real IP or hostname of each node to generate docker compose files in the other nodes.
3. The services would talk with each other, so they need map the /etc/hosts file or add the `extra_hosts` to the docker compose file.
4. We must start the IoTDB services of `iotdb-1` first at the first time of starting.
Expand Down
14 changes: 7 additions & 7 deletions src/UserGuide/Master/QuickStart/ClusterQuickStart.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -72,10 +72,10 @@ Modify the specified configuration file according to the table below:
| Configuration| Configuration Option | IP:192.168.132.10 | IP:192.168.132.11 | IP:192.168.132.12 |
|------------|:-------------------------------|----------------------|----------------------|:---------------------|
| iotdb-confignode.properties | cn\_internal\_address | 192.168.132.10 | 192.168.132.11 | 192.168.132.12 |
| | cn\_target\_config\_node\_list | 192.168.132.10:10710 | 192.168.132.10:10710 | 192.168.132.10:10710 |
| | cn\_seed\_config\_node | 192.168.132.10:10710 | 192.168.132.10:10710 | 192.168.132.10:10710 |
| iotdb-datanode.properties | dn\_rpc\_address | 192.168.132.10 | 192.168.132.11 | 192.168.132.12 |
| | dn\_internal\_address | 192.168.132.10 | 192.168.132.11 | 192.168.132.12 |
| | dn\_target\_config\_node\_list | 192.168.132.10:10710 | 192.168.132.10:10710 | 192.168.132.10:10710 |
| | dn\_seed\_config\_node | 192.168.132.10:10710 | 192.168.132.10:10710 | 192.168.132.10:10710 |

**Notice:**
It's recommended that the configurations of iotdb-common.properties and the heap size of JVM in all nodes are the same.
Expand All @@ -84,7 +84,7 @@ It's recommended that the configurations of iotdb-common.properties and the heap
Before starting the IoTDB cluster, make sure the configurations are correct and there is no any data in the working directory.

#### 1.3.1. start the first node
That is `cn_target_config_node_list` in above configuration table.
That is `cn_seed_config_node` in above configuration table.
Execute these commands below in node of `192.168.132.10`.
```shell
cd /data/iotdb
Expand All @@ -99,7 +99,7 @@ tail -f logs/log_datanode_all.log
If there is no such logs mentioned abolve or there are some `Exception`s in log files, it's failed. Then please check `log_confignode_all.log` and `log_datanode_all.log` in directory of `/data/iotdb/logs`.

**Notice**：
- Make sure the first node, especially the first ConfigNode that `cn_target_config_node_list` specified, starting successfully, and then start the other services.
- Make sure the first node, especially the first ConfigNode that `cn_seed_config_node` specified, starting successfully, and then start the other services.
- If starting failed，it's necessary to do [cleanup](#【reference】cleanup) before starting again.
- How to start service ConfigNode or DataNode alone:
```shell
Expand Down Expand Up @@ -173,7 +173,7 @@ It's the same as starting the other nodes mentioned above. That is downloading I
**Notice**
- It's must be cleaned up, in other words doing [cleanup](#cleanup) in it.
- `cluster_name` of `iotdb-common.properties` must be the same to the cluster.
- `cn_target_config_node_list` and `dn_target_config_node_list` must be the same to the cluster.
- `cn_seed_config_node` and `dn_seed_config_node` must be the same to the cluster.
- The old data wouldn't be moved to the new node but the new data would be.

### 2.1. configuration
Expand All @@ -182,10 +182,10 @@ Modify the specified configuration file according to the table below:
| Configuration | Configuration Option| IP:192.168.132.13 |
|------------|:-------------------------------|:---------------------|
| iotdb-confignode.properties | cn\_internal\_address | 192.168.132.13 |
| | cn\_target\_config\_node\_list | 192.168.132.10:10710 |
| | cn\_seed\_config\_node | 192.168.132.10:10710 |
| iotdb-datanode.properties | dn\_rpc\_address | 192.168.132.13 |
| | dn\_internal\_address | 192.168.132.13 |
| | dn\_target\_config\_node\_list | 192.168.132.10:10710 |
| | dn\_seed\_config\_node | 192.168.132.10:10710 |

### 2.2. expand
Execute commands below in new node of `192.168.132.13`:
Expand Down
6 changes: 3 additions & 3 deletions src/UserGuide/Master/Reference/Common-Config-Manual.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -147,11 +147,11 @@ Different configuration parameters take effect in the following three ways:
| Default | 1 |
| Effective | After restarting system |

* data\_region\_per\_processor
* data\_region\_per\_data\_node

| Name | data\_region\_per\_processor |
| Name | data\_region\_per\_data\_node |
|:-----------:|:--------------------------------------------------------------------------|
| Description | The maximum number of DataRegion expected to be managed by each processor |
| Description | The maximum number of DataRegion expected to be managed by each DataNode |
| Type | double |
| Default | 1.0 |
| Effective | After restarting system |
Expand Down
Loading

0 comments on commit 27ed000

Please sign in to comment.