The cubrid.conf file that has general information on configuring CUBRID is located in the $CUBRID/conf directory. This section explains the cubrid.conf parameters used by CUBRID HA.
A parameter used to configure whether to use CUBRID HA feature. The default value is off.
The ha_mode parameter can be re-configured in the [@<database>] section; however, only off can be entered in the case. An error will be outputted if a value other than off is entered in the [@<database>] section.
If ha_mode is on, the CUBRID HA values are configured by reading cubrid_ha.conf.
This parameter cannot be modified dynamically. To modify the value of this parameter, you must restart the corresponding node.
This parameter configures the minimum number of archive log files to be archived when the value of media_failure_support is yes. The minimum value is 0, and the default is INT_MAX. The performance of the parameter is affected by force_remove_log_archives.
The existing archive log files to which the activated transaction refers or the archive log files of the master node not reflected to the slave node in HA environment will not be deleted. For more information, see the following force_remove_log_archives.
For more information about log_max_archives, see Logging-related Parameters.
It is recommended to always maintain the archive logs needed to perform the HA related process by setting a value for force_remove_log_archives to no in order to implement the HA environment by setting a value for ha_mode to on.
If you set for force_remove_log_archives to yes, the archive log files which will be used in the HA related process can be deleted, and this may lead to an inconsistency between replicated databases. If you want to maintain free disk space even with this risk, set for force_remove_log_archives to yes.
For more information about force_remove_log_archives, see Logging-related Parameters.
A parameter used to specify the maximum number of clients to be connected to a database server simultaneously. The default is 50.
Because the replication log copy process and the replication log reflection process are started by default if CUBRID HA feature is used, you must configure the value to twice the number of all nodes in the CUBRID HA group, except the corresponding node. Furthermore, you must consider the case in which a client that was connected to another node at the time of failover attempts to connect to that node.
The following is an example of configuring cubrid.conf: