As part of the ClustrixDB Installation process you made some configuration selections which are written to clxnode.conf. Post-installation, you can modify the configuration by editing the file on each node while ensuring that the options specified are the same (other than node specific items like BACKEND_ADDR).
The clxnode.conf is stored on each node in /etc/clustrix/ and options specified during installation are written to this file. The following table summarizes these options and provides information on how they can be modified post-installation.
The steps outlined in this document apply to most installations of ClustrixDB, but do not apply to deployments based on the Clustrix AWS AMI.
ClustrixDB requires that all nodes have identical configurations (other than node specific items like BACKEND_ADDR). Modifications to any of the options described below must be made on every node in the cluster. Values commented out with a # will have no effect on the database. Changes to the configuration requires a restart of ClustrixDB services (see below) to take effect.
Use standard bash conventions for clxnode.conf. The file should contain variable definitions, comments, and blank lines only. Option and value settings should not contain any extraneous spaces. For example CPU_CORES=4
|Option||Description||Default Value||To Modify|
|NODE_MEMORY||Memory to use for ClustrixDB, in MiB||auto detected|
|MAX_REDO||Maximum ClustrixDB Redo Space, in MiB||1024||Only modify this variable with guidance from Clustrix Support.|
|CPU_CORES||Number of CPU cores ClustrixDB will use||All|
For additional info, please see section below on setting CPU_CORES.
|DATA_PATH||ClustrixDB Database Storage Path||/data/clustrix|
|DATA_ALLOCATE||Storage space to pre-allocate to ClustrixDB||80% of free space on $DATA_PATH volume ||This value here is used for initialization only. To allocate more space on a node that already has ClustrixDB installed, see ALTER CLUSTER RESIZE DEVICES|
|LOG_PATH||ClustrixDB Logs Path||/data/clustrix/log|
|UI_LOGDIR||ClustrixDB WebUI Logs Path||/data/clustrix/log/clustrix_ui|
|UI_CACHEDIR||ClustrixDB WebUI Cache Path||/var/cache/clustrix/django||Only modify this variable with guidance from Clustrix Support.|
|UNIX_SOCKET_PATH||ClustrixDB MySQL Protocol Unix Socket||/var/lib/mysql/mysql.sock||Only modify this variable with guidance from Clustrix Support.|
|LISTEN_ADDR||ClustrixDB Database Listen Address (Front-End IP) Interface||0.0.0.0|
|MYSQL_PORT||ClustrixDB Database MySQL Port||3306|
|BACKEND_ADDR||ClustrixDB Private Back-End IP Interface||auto detected||See section below on changing BACKEND_ADDR.|
|BACKEND_PORT||ClustrixDB Back End Network Port||24378||It is not recommended to modify the default value for the ClustrixDB Back End Network port.|
|HEALTHMON_PORT||The port used for the ClustrixDB health monitor.||3581|
|HTTP_PORT||ClustrixDB WebUI HTTP Port||80|
|NANNY_PORT||ClustrixDB Nanny Port||2424||It is not recommended to modify the default value for the ClustrixDB nanny port.|
|CONTROL_PORT||ClustrixDB Control Port||2048||It is not recommended to modify the default value for the ClustrixDB control port.|
|CLX_USER||ClustrixDB OS User||root||Do not modify this value after installation.|
|MANAGE_USER||ClustrixDB Manager User||root||Do not modify this value after installation.|
|WRITE_HOSTS||Allow ClustrixDB to modify sshd_config and /etc/hosts.|
This used by root installations only, for internode communication for administrative tasks, including upgrades.
ClustrixDB enables HugeTLB memory allocation for faster startup. NOTE: This causes instability on some systems (particularly certain virtual machines).
Required for non-root installations that have more than 20GiB of $NODE_MEMORY
Contact Clustrix Support before changing from default.
The following options are NOT included by default in clxnode.conf, but can be added to the end of that file to modify behavior from the default. ClustrixDB must be restarted for changes to take effect.
|Option||Description||Default Value||To Modify|
|DISABLE_MULTIPORT||When this option is present, the multiport feature is disabled.||This option is not included in clxnode.conf, resulting in multiport being enabled by default.|
To disable multiport, add an entry for DISABLE_MULTIPORT = Y.
|MULTIPAGE_ALLOC||Bytes reserved for multi-page allocators.||The option is not included clxnode.conf, resulting in a value of 1GiB||Add this entry and define the number of bytes that Clustrix Support recommends for your workload.|
ClustrixDB requires that all nodes must have the same values in clxnode.conf
To apply the changes that have been made to clxnode.conf, the ClustrixDB services on all the nodes will need to be restarted:
shell> /opt/clustrix/bin/clx dbrestart
The default setting of CPU_CORES=All will make use of all available cores in the system. If you would like to limit the number of cores utilized by ClustrixDB you must modify the value for CPU_CORES to specify the number of cores that should be used. ClustrixDB licensing will base its enforcement on the number of cores being utilized in the system as specified by CPU_CORES.
Run the clx command to ensure it has cached the IP address of each node.
shell> /opt/clustrix/bin/clx cmd 'clx cache'