When you install Scylla Manager, it installs a local instance of Scylla to use as it’s database. You are not required to use the local instance and can use Scylla Manager with a remote database.
Scylla cluster to be used as Scylla Manager data store.
scylla-manager package is a meta-package that pulls both Scylla and Scylla Manager packages.
If you do not intend to use the local Scylla instance, you may remove it.
sudo yum remove scylla-enterprise -y
Remove related packages. This would also remove the Scylla Manager.
sudo yum autoremove -y
Install the Scylla Manager client and server packages.
sudo yum install scylla-manager-client scylla-manager-server -y
Scylla Manager configuration file
/etc/scylla-manager/scylla-manager.yaml contains a database configuration section.
# Scylla Manager database, used to store management data. database: hosts: - 127.0.0.1 # Database credentials. # user: user # password: password # Database connection timeout. # timeout: 600ms # Keyspace for management data, for create statement see /etc/scylla-manager/create_keyspace.cql.tpl. # keyspace: scylla_manager # replication_factor: 1
Using an editor, open the file, and change relevant parameters.
hosts parameter, change the IP address to the IP address or addresses of the remote cluster.
If authentication is needed, uncomment and edit the
If the remote cluster contains more than one node, uncomment and edit the
replication_factor parameter to match the required replication factor.
Note that this would use a simple replication strategy (SimpleStrategy).
If you want to use a different replication strategy, create
scylla_manager keyspace (or another matching the
keyspace parameter) yourself.
Refer to Scylla Architecture - Fault Tolerance for more information on replication.
The sample configuration of Scylla Manager working with a remote cluster with authentication and replication factor 3 could look like this.
database: hosts: - 22.214.171.124 - 126.96.36.199 user: user password: password replication_factor: 3