This article uses a local environment as an example to illustrate how to start, expand, and shrink an IoTDB Cluster.
Notice: This document is a tutorial for deploying in a pseudo-cluster environment using different local ports, and is for exercise only. In real deployment scenarios, you only need to configure the IPV4 address or domain name of the server, and do not need to change the Node ports.
Unzip the apache-iotdb-1.0.0-all-bin.zip file to cluster0 folder.
Start the Cluster version with one ConfigNode and one DataNode(1C1D), and the default number of replicas is one.
./cluster0/sbin/start-confignode.sh ./cluster0/sbin/start-datanode.sh
./cluster0/sbin/start-cli.sh
IoTDB> show cluster details +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ |NodeID| NodeType| Status|InternalAddress|InternalPort|ConfigConsensusPort|RpcAddress|RpcPort|DataConsensusPort|SchemaConsensusPort|MppPort| +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ | 0|ConfigNode|Running| 127.0.0.1| 22277| 22278| | | | | | | 1| DataNode|Running| 127.0.0.1| 9003| | 127.0.0.1| 6667| 40010| 50010| 8777| +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ Total line number = 2 It costs 0.242s
Unzip the apache-iotdb-1.0.0-all-bin.zip file to cluster1 and cluster2 folder.
For folder cluster1:
| configuration item | value |
|---|---|
| cn_internal_address | 127.0.0.1 |
| cn_internal_port | 22279 |
| cn_consensus_port | 22280 |
| cn_target_config_node_list | 127.0.0.1:22277 |
| configuration item | value |
|---|---|
| dn_rpc_address | 127.0.0.1 |
| dn_rpc_port | 6668 |
| dn_internal_address | 127.0.0.1 |
| dn_internal_port | 9004 |
| dn_mpp_data_exchange_port | 8778 |
| dn_data_region_consensus_port | 40011 |
| dn_schema_region_consensus_port | 50011 |
| dn_target_config_node_list | 127.0.0.1:22277 |
For folder cluster2:
| configuration item | value |
|---|---|
| cn_internal_address | 127.0.0.1 |
| cn_internal_port | 22281 |
| cn_consensus_port | 22282 |
| cn_target_config_node_list | 127.0.0.1:22277 |
| configuration item | value |
|---|---|
| dn_rpc_address | 127.0.0.1 |
| dn_rpc_port | 6669 |
| dn_internal_address | 127.0.0.1 |
| dn_internal_port | 9005 |
| dn_mpp_data_exchange_port | 8779 |
| dn_data_region_consensus_port | 40012 |
| dn_schema_region_consensus_port | 50012 |
| dn_target_config_node_list | 127.0.0.1:22277 |
Expanding the Cluster to three ConfigNode and three DataNode(3C3D). The following commands can be executed in arbitrary order.
./cluster1/sbin/start-confignode.sh ./cluster1/sbin/start-datanode.sh ./cluster2/sbin/start-confignode.sh ./cluster2/sbin/start-datanode.sh
Execute the show cluster details command, then the result is shown below:
IoTDB> show cluster details +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ |NodeID| NodeType| Status|InternalAddress|InternalPort|ConfigConsensusPort|RpcAddress|RpcPort|DataConsensusPort|SchemaConsensusPort|MppPort| +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ | 0|ConfigNode|Running| 127.0.0.1| 22277| 22278| | | | | | | 2|ConfigNode|Running| 127.0.0.1| 22279| 22280| | | | | | | 3|ConfigNode|Running| 127.0.0.1| 22281| 22282| | | | | | | 1| DataNode|Running| 127.0.0.1| 9003| | 127.0.0.1| 6667| 40010| 50010| 8777| | 4| DataNode|Running| 127.0.0.1| 9004| | 127.0.0.1| 6668| 40011| 50011| 8778| | 5| DataNode|Running| 127.0.0.1| 9005| | 127.0.0.1| 6669| 40012| 50012| 8779| +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ Total line number = 6 It costs 0.012s
# Removing by ip:port ./cluster0/sbin/remove-confignode.sh 127.0.0.1:22279 # Removing by Node index ./cluster0/sbin/remove-confignode.sh 2
# Removing by ip:port ./cluster0/sbin/remove-datanode.sh 127.0.0.1:6668 # Removing by Node index ./cluster0/sbin/remove-confignode.sh 4
Execute the show cluster details command, then the result is shown below:
IoTDB> show cluster details +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ |NodeID| NodeType| Status|InternalAddress|InternalPort|ConfigConsensusPort|RpcAddress|RpcPort|DataConsensusPort|SchemaConsensusPort|MppPort| +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ | 0|ConfigNode|Running| 127.0.0.1| 22277| 22278| | | | | | | 3|ConfigNode|Running| 127.0.0.1| 22281| 22282| | | | | | | 1| DataNode|Running| 127.0.0.1| 9003| | 127.0.0.1| 6667| 40010| 50010| 8777| | 5| DataNode|Running| 127.0.0.1| 9005| | 127.0.0.1| 6669| 40012| 50012| 8779| +------+----------+-------+---------------+------------+-------------------+----------+-------+-----------------+-------------------+-------+ Total line number = 4 It costs 0.005s