You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Keyspace for management data, for create statement see /etc/scylla-manager/create_keyspace.cql.tpl.
116
116
# keyspace: scylla_manager
117
-
# replication_factor: 1
118
117
119
118
Using an editor open the file and change relevant parameters.
120
119
@@ -124,8 +123,10 @@ Using an editor open the file and change relevant parameters.
124
123
125
124
#. If authentication is needed, uncomment and edit the ``user`` and ``password`` parameters.
126
125
127
-
#. If it's a single DC cluster, uncomment and edit the ``replication_factor`` parameter to match the required replication factor.
128
-
This would use NetworkTopologyStrategy to create a ScyllaDB Manager keyspace, refer to `ScyllaDB Architecture - Fault Tolerance <https://docs.scylladb.com/architecture/architecture-fault-tolerance/>`_ for more information on replication.
126
+
#. If it's a single DC cluster, ScyllaDB Manager keyspace using NetworkTopologyStrategy would be created.
127
+
Refer to `ScyllaDB Architecture - Fault Tolerance <https://docs.scylladb.com/architecture/architecture-fault-tolerance/>`_ for more information on replication.
128
+
It would have replication factor equal to the amount of racks in each data center. In case where this setup could lead to reduced availability
129
+
(total replication factor smaller than 3), replication factor will be increased up to 3 (depending on node count) regardless of the rack count.
129
130
130
131
#. If it's a multi DC cluster, create a keyspace named ``scylla_manager`` yourself.
131
132
You can use a different keyspace name, just remember to adjust the ``keyspace`` parameter value.
@@ -159,7 +160,6 @@ Sample configuration of ScyllaDB Manager working with a remote cluster with auth
0 commit comments