Configuring and Starting Broker, and Verifying the Broker Status

Configuring the Broker

To provide normal service during a server failover, it is necessary to configure an available node in the db-host of databases.txt. If the user does not specify it, the ACCESS_MODE of the broker will be configured to Read Write mode by default.

#db-name        vol-path                db-host         log-path

demodb          /home1/cubrid1/DB/demodb nodeA:nodeB       /home1/cubrid1/DB/demodb/log

Starting Broker and Verifying its Status

Because the broker is for the JDBC or CCI application to access, you do not need to start the broker for a simple CUBRID HA test. You can start the broker with cubrid broker start and stop it with cubrid broker stop.

The following example shows how to execute a broker from the master node.

[master]$ cubrid broker start

@ cubrid broker start

++ cubrid broker start: success

[master]$ cubrid broker status

@ cubrid broker status

% query_editor OFF

% demodb  - cub_cas [9531,33000] /home1/cubrid1/CUBRID/log/broker//demodb.access /home1/cubrid1/CUBRID/log/broker//demodb.err

 JOB QUEUE:0, AUTO_ADD_APPL_SERVER:ON, SQL_LOG_MODE:ALL:100000

 LONG_TRANSACTION_TIME:60.00, LONG_QUERY_TIME:60.00, SESSION_TIMEOUT:300

 KEEP_CONNECTION:AUTO, ACCESS_MODE:RW

---------------------------------------------------------

ID   PID   QPS   LQS PSIZE STATUS

---------------------------------------------------------

 1  9532     0     0  48120  IDLE