Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

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



Managing a Specific Broker

Enter the code below to run broker1 only. Note that broker1 should have been configured in the shared memory.

% cubrid broker on broker1

The following message is returned if broker1 is not configured in the shared memory.

% cubrid broker on broker1

Cannot open shared memory

Enter the code below to stop broker1 only. Note that service pool of broker1 is also removed.

% cubrid broker off broker1

Enter the code below to restart broker1.

% cubrid broker restart broker1

The broker reset feature enables broker application servers (CAS) to disconnect the existing connection and reconnect when the servers are connected to unwanted databases due to failover and etc in HA. For example, once Read Only broker is connected to active servers, it is not automatically connected to standby servers although standby servers are available. Connecting to standby servers is allowed only with the cubrid broker reset command.

Enter the code below to reset broker1.

% cubrid broker reset broker1