The operation scenario written in this page is only applied to read service. It is required to allow read service only or dynamically change mode configuration of broker to Read Only. There can be two types of operation scenarios in which failover occurs or it does not occur.
You can perform the following operations without stopping and restarting nodes in CUBRID HA group.
General Operation |
Scenario |
Consideration |
---|---|---|
Schema change (primary key change) |
When an operation task is performed at the master node, it is automatically reflected to the slave node. |
In order to change the primary key, the existing key must be deleted and a new one added. For this reason, replication reflection may not occur due to the HA internal structure which reflects primary key-based replication logs. Therefore, operation tasks must be performed during the read service. |
You must stop nodes in CUBRID HA group and complete operation before performing the following operations.
General Operation |
Scenario |
Consideration |
---|---|---|
DBMS version upgrade |
Restart each node and broker in the CUBRID HA group after they are upgraded. |
A version upgrade means that there have been changes in the internal protocol, volume, or log of CUBRID. |
Schema change, index change, and authorization change |
Stop the node that must be changed, perform an operation task, and then execute the node. |
Although this operation task can be executed in an operation scenario without failover during the read and write service, it takes a long time to execute. |
Massive data processing (INSERT / UPDATE / DELETE) |
Stop the node that must be changed, perform an operation task, and then execute the node. |
This processes massive data that cannot be segmented. |