Fedora, CentOS, or Red Hat
This section describes the steps needed to set up a multi-node Citus cluster on your own Linux machines from RPM packages.
Steps to be executed on all nodes
1. Add repository
# Add Citus repository for package manager curl https://install.citusdata.com/community/rpm.sh | sudo bash
2. Install PostgreSQL + Citus and initialize a database
# install PostgreSQL with Citus extension sudo yum install -y citus121_16 # initialize system database sudo /usr/pgsql-16/bin/postgresql-16-setup initdb # preload citus extension echo "shared_preload_libraries = 'citus'" | sudo tee -a /var/lib/pgsql/16/data/postgresql.conf
PostgreSQL adds version-specific binaries in /usr/pgsql-16/bin, but you’ll usually just need psql, whose latest version is added to your path, and managing the server itself can be done with the service command.
3. Configure connection and authentication
Before starting the database let’s change its access permissions. By default the database server listens only to clients on localhost. As a part of this step, we instruct it to listen on all IP interfaces, and then configure the client authentication file to allow all incoming connections from the local network.
sudo vi /var/lib/pgsql/16/data/postgresql.conf
# Uncomment listen_addresses for the changes to take effect listen_addresses = '*'
sudo vi /var/lib/pgsql/16/data/pg_hba.conf
# Allow unrestricted access to nodes in the local network. The following ranges # correspond to 24, 20, and 16-bit blocks in Private IPv4 address spaces. host all all 10.0.0.0/8 trust # Also allow the host unrestricted access to connect to itself host all all 127.0.0.1/32 trust host all all ::1/128 trust
Your DNS settings may differ. Also these settings are too permissive for some environments, see our notes about Increasing Worker Security. The PostgreSQL manual explains how to make them more restrictive.
4. Start database servers, create Citus extension
# start the db server sudo service postgresql-16 restart # and make it start automatically when computer does sudo chkconfig postgresql-16 on
You must add the Citus extension to every database you would like to use in a cluster. The following example adds the extension to the default database which is named postgres.
sudo -i -u postgres psql -c "CREATE EXTENSION citus;"
Steps to be executed on the coordinator node
The steps listed below must be executed only on the coordinator node after the previously mentioned steps have been executed.
1. Add worker node information
We need to inform the coordinator about its workers. To add this information, we call a UDF which adds the node information to the pg_dist_node catalog table, which the coordinator uses to get the list of worker nodes. For our example, we assume that there are two workers (named worker-101, worker-102). Add the workers’ DNS names (or IP addresses) and server ports to the table.
# Register the hostname that future workers will use to connect # to the coordinator node. # # You'll need to change the example, 'coord.example.com', # to match the actual hostname sudo -i -u postgres psql -c \ "SELECT citus_set_coordinator_host('coord.example.com', 5432);" # Add the worker nodes. # # Similarly, you'll need to change 'worker-101' and 'worker-102' to the # actual hostnames sudo -i -u postgres psql -c "SELECT * from citus_add_node('worker-101', 5432);" sudo -i -u postgres psql -c "SELECT * from citus_add_node('worker-102', 5432);"
2. Verify that installation has succeeded
To verify that the installation has succeeded, we check that the coordinator node has picked up the desired worker configuration. This command when run in the psql shell should output the worker nodes we added to the pg_dist_node table above.
sudo -i -u postgres psql -c "SELECT * FROM citus_get_active_worker_nodes();"
Ready to use Citus
At this step, you have completed the installation process and are ready to use your Citus cluster. The new Citus database is accessible in psql through the postgres user:
sudo -i -u postgres psql