Skip to main content
Once the cluster configuration file is defined, and every module across the cluster has a copy of the cluster.config with its module-specific configuration, proceed to start the cluster services. A systemd service is installed with each module RPM package. The service names follow the pattern regatta-1.0-<module name>, for example: regatta-1.0-rdb. For a single-node deployment, start all services with the following command:
For a multi-node deployment, an additional file should be created for each RDB module named rdb.config, alongside the cluster.config file:
The file should contain the ID assigned to the RDB module on the current node, as defined in the configuration file:
For example, if in the configuration file the module ID was defined as follows:
Then the rdb.config file should contain the following line:
Once the rdb.config file is present for each RDB module across the cluster nodes, proceed to start the services on each of the cluster nodes:
Where module is one of the Regatta software modules. For example:
You can verify that the cluster is running by checking the Regatta services on any node:
Example outuput (each Regatta module runs under its own service, such as regatta-1.0-rdb.service):
Congratulations! Your Regatta cluster is up and running. Now you can connect your application using your preferred client.