Prerequisite
Note: Please install MinGW or WSL or git bash if you are using Windows.
Example of distributed configurations for 1 node and 1 replica
Compile from source code:
1. mvn clean package -DskipTests
2. chmod -R 777 ./cluster/target/
3. nohup ./cluster/target/iotdb-cluster-0.13.0-SNAPSHOT/sbin/start-node.sh >/dev/null 2>&1 &
Use the official website release version:
1. curl -O https://downloads.apache.org/iotdb/0.12.1/apache-iotdb-0.12.1-cluster-bin.zip
2. unzip apache-iotdb-0.12.1-cluster-bin.zip
3. cd apache-iotdb-0.12.1-cluster-bin
4. sed -i -e 's/^seed_nodes=127.0.0.1:9003,127.0.0.1:9005,127.0.0.1:9007$/seed_nodes=127.0.0.1:9003/g' conf/iotdb-cluster.properties
5. sed -i -e 's/^default_replica_num=3$/default_replica_num=1/g' conf/iotdb-cluster.properties
6. nohup ./sbin/start-node.sh >/dev/null 2>&1 &
Example of distributed configurations for 3 nodes and 1 replica on a single machine
Configurations
You can start multiple instances on a single machine by modifying the configurations yourself to handling port and file directory conflicts.
Node1:(default)
iotdb-cluster.properties
1. seed_nodes = 127.0.0.1:9003,127.0.0.1:9005,127.0.0.1:9007
2. default_replica_num = 1
3. internal_meta_port = 9003
4. internal_data_port = 40010
iotdb-engine.properties
1. rpc_port=6667
Node2:
iotdb-cluster.properties
1. seed_nodes = 127.0.0.1:9003,127.0.0.1:9005,127.0.0.1:9007
2. default_replica_num = 1
3. internal_meta_port = 9005
4. internal_data_port = 40012
iotdb-engine.properties
1. rpc_port=6669
Node3:
iotdb-cluster.properties
1. seed_nodes = 127.0.0.1:9003,127.0.0.1:9005,127.0.0.1:9007
2. default_replica_num = 1
3. internal_meta_port = 9007
4. internal_data_port = 40014
iotdb-engine.properties
1. rpc_port=6671
Compile from source code:
1. mvn clean package -DskipTests
2. chmod -R 777 ./cluster/target/
3. nohup ./cluster/target/iotdb-cluster-0.13.0-SNAPSHOT/sbin/start-node.sh ./cluster/target/test-classes/node1conf/ >/dev/null 2>&1 &
4. nohup ./cluster/target/iotdb-cluster-0.13.0-SNAPSHOT/sbin/start-node.sh ./cluster/target/test-classes/node2conf/ >/dev/null 2>&1 &
5. nohup ./cluster/target/iotdb-cluster-0.13.0-SNAPSHOT/sbin/start-node.sh ./cluster/target/test-classes/node3conf/ >/dev/null 2>&1 &
Use the official website release version:
Download the release version:
1. curl -O https://downloads.apache.org/iotdb/0.12.1/apache-iotdb-0.12.1-cluster-bin.zip
Unzip the package:
1. unzip apache-iotdb-0.12.1-cluster-bin.zip
Enter IoTDB cluster root directory:
1. cd apache-iotdb-0.12.1-cluster-bin
Set default_replica_num = 1:
1. sed -i -e 's/^default_replica_num=3$/default_replica_num=1/g' conf/iotdb-cluster.properties
Create conf_dir for node2 and node3:
1. cp -r conf node2_conf
2. cp -r conf node3_conf
Handle port and file directory conflicts:
1. sed -i -e 's/^internal_meta_port=9003$/internal_meta_port=9005/g' -e 's/^internal_data_port=40010$/internal_data_port=40012/g' node2_conf/iotdb-cluster.properties
2. sed -i -e 's/^internal_meta_port=9003$/internal_meta_port=9007/g' -e 's/^internal_data_port=40010$/internal_data_port=40014/g' node3_conf/iotdb-cluster.properties
3. sed -i -e 's/^rpc_port=6667$/rpc_port=6669/g' -e node2_conf/iotdb-engine.properties
4. sed -i -e 's/^rpc_port=6667$/rpc_port=6671/g' -e node3_conf/iotdb-engine.properties
5. sed -i -e 's/^# data_dirs=data\/data$/data_dirs=node2\/data/g' -e 's/^# wal_dir=data\/wal$/wal_dir=node2\/wal/g' -e 's/^# tracing_dir=data\/tracing$/tracing_dir=node2\/tracing/g' -e 's/^# system_dir=data\/system$/system_dir=node2\/system/g' -e 's/^# udf_root_dir=ext\/udf$/udf_root_dir=node2\/ext\/udf/g' -e 's/^# index_root_dir=data\/index$/index_root_dir=node2\/index/g' node2_conf/iotdb-engine.properties
6. sed -i -e 's/^# data_dirs=data\/data$/data_dirs=node3\/data/g' -e 's/^# wal_dir=data\/wal$/wal_dir=node3\/wal/g' -e 's/^# tracing_dir=data\/tracing$/tracing_dir=node3\/tracing/g' -e 's/^# system_dir=data\/system$/system_dir=node3\/system/g' -e 's/^# udf_root_dir=ext\/udf$/udf_root_dir=node3\/ext\/udf/g' -e 's/^# index_root_dir=data\/index$/index_root_dir=node3\/index/g' node3_conf/iotdb-engine.properties
You can modify the configuration items by yourself instead of using “sed” command
Start the three nodes with their configurations:
1. nohup ./sbin/start-node.sh >/dev/null 2>&1 &
2. nohup ./sbin/start-node.sh ./node2_conf/ >/dev/null 2>&1 &
3. nohup ./sbin/start-node.sh ./node3_conf/ >/dev/null 2>&1 &
Example of distributed configurations for 3 nodes and 3 replicas
Suppose we need to deploy the distributed IoTDB on three physical nodes, A, B, and C, whose public network IP is A_public_IP, B_public_IP, and C_public_IP, and private network IP is A_private_IP, B_private_IP, and C_private_IP.
Note: If there is no public network IP or private network IP, both can be set to the same, just need to ensure that the client can access the server. The private ip corresponds to configuration iteminternal_ ipin iotdb-cluster.properties, and the public ip corresponds to configuration itemrpc_ address in iotdb-engine.properties.
Configurations
NodeA:
iotdb-cluster.properties
1. seed_nodes = A_private_Ip:9003,B_private_Ip:9003,C_private_Ip:9003
2. default_replica_num = 3
3. internal_meta_port = 9003
4. internal_data_port = 40010
5. internal_ip = A_private_Ip
iotdb-engine.properties
1. rpc_port = 6667
2. rpc_address = A_public_ip
NodeB:
iotdb-cluster.properties
1. seed_nodes = A_private_Ip:9003,B_private_Ip:9003,C_private_Ip:9003
2. default_replica_num = 3
3. internal_meta_port = 9003
4. internal_data_port = 40010
5. internal_ip = B_private_Ip
iotdb-engine.properties
1. rpc_port = 6667
2. rpc_address = B_public_ip
NodeC:
iotdb-cluster.properties
1. seed_nodes = A_private_Ip:9003,B_private_Ip:9003,C_private_Ip:9003
2. default_replica_num = 3
3. internal_meta_port = 9003
4. internal_data_port = 40010
5. internal_ip = C_private_Ip
iotdb-engine.properties
1. rpc_port = 6667
2. rpc_address = C_public_ip
Start IoTDB cluster
The operation steps are as follows:
- Use ‘mvn clean package -pl cluster -am -DskipTests’ to compile the distributed module or directly go into the website
(opens new window) to download the latest version. - Make sure ports 6567, 6667, 9003, 9004, 40010, 40011 and 31999 are open on all three nodes.
- Send the package to all servers.
- Modify the configuration items.
- Run sh sbin/start-node.sh on each of the three nodes (or run in the background).
Compile from source code:
1. mvn clean package -DskipTests
2. chmod -R 777 ./cluster/target/
3. cd cluster/target/iotdb-cluster-0.13.0-SNAPSHOT/
Use the official website release version:
Download the release version:
1. curl -O https://downloads.apache.org/iotdb/0.12.4/apache-iotdb-0.12.4-cluster-bin.zip
Unzip the package:
1. unzip apache-iotdb-0.12.4-cluster-bin.zip
Enter IoTDB cluster root directory:
1. cd apache-iotdb-0.12.4-cluster-bin
Set default_replica_num = 3: default value of this configuration item is 3
Set internal_ip = private ip of node (e.g. 192.168.1.1)
1. sed -i -e 's/^internal_ip=127.0.0.1$/internal_ip=192.168.1.1/g' conf/iotdb-cluster.properties
Set seed_node = A_private_Ip:9003,B_private_Ip:9003,C_private_Ip:9003 (e.g. private ip of all three nodes are 192.168.1.1,192.168.1.2,192.168.1.3)
1. sed -i -e 's/^seed_nodes=127.0.0.1:9003,127.0.0.1:9005,127.0.0.1:9007$/seed_nodes=192.168.1.1:9003,192.168.1.2:9003,192.168.1.3:9003/g' conf/iotdb-cluster.properties
Set rpc_address = public ip of node (e.g. 192.168.1.1)
1. sed -i -e 's/^rpc_address=127.0.0.1$/rpc_address=192.168.1.1/g' conf/iotdb-engine.properties
You can modify the configuration items by yourself instead of using “sed” command
Start the three nodes with their configurations:
1. nohup ./sbin/start-node.sh >/dev/null 2>&1 &
