CREATE CLUSTER REPLICA
CREATE CLUSTER REPLICA is deprecated.
We recommend migrating to a managed cluster instead of manually creating and dropping replicas.
CREATE CLUSTER REPLICA provisions a new replica of a cluster.
A cluster consists of zero or more replicas. Each replica of a cluster is a pool of compute resources that performs exactly the same computations on exactly the same data.
Using multiple replicas of a cluster facilitates fault tolerance. Clusters with multiple replicas can tolerate failures of the underlying hardware or network. As long as one replica remains reachable, the cluster as a whole remains available.
|The cluster you want to attach a replica to.
|A name for this replica.
|The size of the replica. For valid sizes, see Size.
|The availability zone of the underlying cloud provider in which to provision the replica. You must specify an AWS availability zone ID in either
use1-az1. Note that you must use the zone’s ID, not its name.
|The interval at which to collect introspection data. See Troubleshooting for details about introspection data. The special value
0 entirely disables the gathering of introspection data.
|Whether to introspect the gathering of the introspection data.
IDLE ARRANGEMENT MERGE EFFORT
|Unstable. This option may be changed or removed at any time.
The amount of effort the replica should exert on compacting arrangements during idle periods.
SIZE option for replicas is identical to the
SIZE option for
clusters option, except that the size
applies only to the new replica.
The replica will consume credits at a rate determined by its size:
|Credits per hour
Credit usage is measured at a one second granularity. Credit usage begins when a
CREATE CLUSTER REPLICA provisions the replica and ends when a
DROP CLUSTER REPLICA statement deprovisions the replica.
Homogeneous vs. heterogeneous hardware provisioning
Because Materialize uses active replication, all replicas will be instructed to do the same work, irrespective of their resource allocation.
For the most stable performance, we recommend using the same size and disk configuration for all replicas.
However, it is possible to use different replica configurations in the same cluster. In these cases, the replicas with less resources will likely be continually burdened with a backlog of work. If all of the faster replicas become unreachable, the system might experience delays in replying to requests while the slower replicas catch up to the last known time that the faster machines had computed.
CREATE CLUSTER REPLICA c1.r1 (SIZE = 'medium');
The privileges required to execute this statement are:
- Ownership of