NOTICE: CURRENT IoTDB CLUSTER IS FOR TESTING NOW! PLEASE BE DELIBERATE IF YOU RUN IT IN PRODUCT ENVIRONMENT.
mvn clean package -DskipTests chmod -R 777 ./cluster/target/ nohup ./cluster/target/iotdb-cluster-0.12.0-SNAPSHOT/sbin/start-node.sh ./cluster/target/test-classes/node1conf/ >/dev/null 2>&1 & nohup ./cluster/target/iotdb-cluster-0.12.0-SNAPSHOT/sbin/start-node.sh ./cluster/target/test-classes/node2conf/ >/dev/null 2>&1 & nohup ./cluster/target/iotdb-cluster-0.12.0-SNAPSHOT/sbin/start-node.sh ./cluster/target/test-classes/node3conf/ >/dev/null 2>&1 &
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 operation steps are as follows: