Duplexing Brokers

As a 3-tier DBMS, CUBRID has middleware called the broker which relays applications and database servers. To provide HA, the broker also requires duplicate hardware equipment. This method will prevent any interruptions in a broker in case of occurring a hardware failure.

To use this feature, you must define multiple-broker connections in the connection URL of JDBC. For details, see JDBC Configuration.

Broker failover

JDBC tries to connect to a broker that has the highest priority in the connection URL. If a failure occurs, it tries to connect to the next broker defined in the order of priority of the connection URL. This requires no processing in the application side as it is processed within the JDBC driver.

Broker failback

If the failed broker is recovered after a failover, the connection to the existing broker is terminated and a new connection is established with the recovered broker which has the highest priority. This requires no processing in the application side as it is processed within the JDBC driver. Exeuction time of failback depends on the value configured in JDBC connection URL. For details, see JDBC Configuration.