What is the difference between paired mode and load-balanced mode when configuring high availability?
SingleStore DB stores data redundantly in a set of leaves, called availability groups, to ensure high availability. SingleStore DB handles node failures by promoting the appropriate replica partitions into masters so that your databases remain online. However, if all of your machines fail, then your data is unavailable until you recover enough Leaf nodes in your cluster.
The placement of replica partitions in a cluster can be specified via the
leaf_failover_fanout variable. SingleStore DB supports two modes for partition placement:
paired mode, each leaf in an availability group has a corresponding pair node in the other availability group. When a single leaf fails, the partitions on its paired leaf are promoted to master partitions. As a result, this leaf has all master partitions and no replica partitions. Which increases the overall workload of this leaf by 100%, affecting its performance.
On the other hand,
load_balanced mode places a leaf’s replica partitions evenly across the healthy leaves in the cluster. When a single leaf fails, the partitions on multiple paired leaves are promoted to master partitions. As a result, All leaves have master partitions spreading increased workload to all leaves thus achieving better performance.
For more information, see Managing High Availability.