To prepare the operating system for installation of ClustrixDB, perform the following steps on each node:
Log in to the server as a user with sudo permissions
shell> ssh username@ip_of_1st_server
Verify that the following packages are installed:
|shell> sudo yum install bzip2 xz wget screen ntp ntpdate vim htop mdadm|
If you are using RHEL, edit the following repo file:
|shell>sudo yum-config-manager --enable rhui-REGION-rhel-server-optional|
Clustrix recommends the following file system configuration:
ClustrixDB requires database files to be stored on a local SSD-based file system on a separate volume from the root volume containing the OS. This volume should be configured with RAID-0 for best performance and include all of the SSDs to be used for ClustrixDB. For redundancy, ClustrixDB already writes by default two copies of the data so in the event of a node failure or disk failure, the data is still available and don't require higher RAID volume types as that may impact performance. Clustrix recommends using the default mount point of /data to simplify installation.
Less performant disks may be used for logs.
Mechanical disks and network-attached storage lack sufficient performance to be used for ClustrixDB data (i.e. /data mount point) and are not supported.
Root Volume / OS
See also Example File System Configuration.
Ensure ntpd is running and firewalld is not running. Note: if firewalld is not installed, the commands below will return an error, and this would be expected.
|shell> sudo systemctl enable ntpd |
shell> sudo systemctl start ntpd
shell> sudo systemctl disable firewalld
shell> sudo systemctl stop firewalld
ClustrixDB requires that system clocks be synchronized and that NTP be configured on all nodes. The firewalld service should be disabled so nodes can communicate without restriction.
Verify that SELinux is disabled:
SELinux status: disabled
If it is running, prevent SELinux from enabling at reboot by editing /etc/sysconfig/selinux and setting SELINUX=disabled
Then set the currently running SELinux to Permissive mode to effectively disable it until the next reboot.
|shell> setenforce 0|
SELinux status: disabled
We recommend configuring journald to store its logs on disk, instead of in RAM in the tmpfs. Modify /etc/systemd/journald.conf on each node, then reboot for it to take effect:
|shell> cat Storage=persistent /etc/systemd/journald.conf|
Swap should be disabled if it's not already disabled.
identify swap devices and files, disable swap and remove any matching entries in /etc/fstab:
modify /etc/fstab to remove matching entries.
By default ClustrixDB installer will create and configure these users. If you prefer, you can create these users prior to installation, then direct the installer to make use of these users. For more information, see ClustrixDB Operating System Users.
These are the Linux OS user accounts involved with installing and operating ClustrixDB:
Linux OS User
How it is used
Runs the initial installation of the ClustrixDB software. The installation can be run indirectly through sudo privileges granted to another Linux user. Subsequent upgrades of ClustrixDB do not need root-level permissions.
The ClustrixDB processes run as the clxd Linux user. This is a daemon account, and therefore administrators should not log into Linux using this account. The one exception is when performing ClustrixDB upgrades, the upgrade is executed as the clxd Linux user.
This Linux user is intended to be used by administrators to work with the ClustrixDB software. This user is typically configured to have its environment set for convenient use of the ClustrixDB command-line tools.
Now that you have prepared your OS, proceed to Install ClustrixDB.