Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.4.0 |  CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 

Operation Scenario during Read Service

This operation scenario provides only the read service for operation tasks. It is necessary to allow only the read service, or to dynamically change the mode of the broker to Read Only. The operation scenario during the read service can be divided into two groups: operation scenarios with failover, and operation scenarios without failover.

Operation Scenario without Failover

The following task can be performed without terminating and restarting nodes in the CUBRID HA group.

Most common operation tasks



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.

Operation Scenario with Failover

The following tasks must be started once all nodes in the CUBRID HA group are terminated and all operation tasks are complete.

Most common operation tasks



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.
Because there are two different versions of the protocols, volumes, and logs of a broker and server during an upgrade, an operation task must be performed to make sure that each client and broker (before/after upgrade) are connected to the corresponding counterpart in the same version.

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.
Therefore, if operation task time becomes an issue, change each node while HA is stopped.

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.