The following assumptions are used in these deployment scenarios:
- The steps in this section are performed on the Insight Views SingleStore data nodes for the Insight Views component deployed alongside ServAssure NXT.
- Network connectivity exists between Insight Views in Site A and Site B.
- SingleStore nodes in both datacenters are started and running as part of normal operation (non-failover mode). Data is replicated between SingleStore in Site A and Site B.
- Network connectivity exists between SingleStore in Site A and Site B. Data is replicated across clusters asynchronously on leaf nodes.
- The recommended minimum network bandwidth is at least 1 MB per second per partition for replication to succeed. You can increase the bandwidth to help prevent timeouts.
- To replicate a database, the secondary cluster must have CREATE DATABASE privilege and the primary cluster must have ALL privileges on the primary cluster’s master aggregator. Kerberos authentication is not supported.
- The two clusters must use the same SingleStore version to support replication. When failover happens, the destination cluster becomes the source cluster.
- The two clusters must be installed with the same user and have the same SSL settings for Kafka Broker nodes. Refer to the Insight Views site_vars file(s) to verify Kafka settings are the same for both clusters.
- Replication is configured at the database level and manually created databases are not replicated. For example, when a new tenant is installed or removed, the same tenant is automatically added to or deleted from the second cluster.
- Unlimited storage databases are not supported for replication.
- The servers that host the Installation Management Server for Ansible must be configured as Site A or Site B. Separate Ansible host_inventory files are required for each site.