The load balancing structure increases the availability of the CUBRID servie by placing several nodes in the HA configuration (one master node and one slave node) and distributes read-load.
Because the replica nodes receive replication logs from the nodes in the HA configuration and maintain the same data, and because the nodes in the HA configuration do not receive replication logs from the replica nodes, its network and disk usage rate is lower than that of the multiple-slave structure.
Because replica nodes are not included in the HA structure, they provide read service without failover, even when all other nodes in the HA structure fail.
You can configure each node in the basic structure of HA as shown below:
You must enter the list of DB server hosts in the order so that each broker can be connected appropriate HA or load balancing server in the databases.txt file of a broker node. The following is an example of the databases.txt file:
#db-name vol-path db-host log-path
testdb1 /home/cubrid/DB/testdb1 nodeA:nodeB /home/cubrid/DB/testdb1/log
testdb2 /home/cubrid/DB/testdb2 nodeC:nodeD /home/cubrid/DB/testdb2/log
The data in the CUBRID HA group may lose integrity when there are multiple failures in this structure.
In addition, if the mode of replication log copy process is ASYNC, the data in the CUBRID HA group may lose integrity.
If the data in the CUBRID HA group loses integrity for any of the reasons above, you can fix it by using Rebuilding Replications.