On this page
Attaches a detached leaf into the cluster, re-introducing its data (if possible).
ATTACH LEAF 'host':port [FORCE] [NO REBALANCE]
ATTACH LEAFwill transition the leaf from the
detachedstate to the
ATTACHis used to reintroduce a leaf back into the system.
ATTACH LEAFalso performs any rebalance and resyncing actions needed to bring the leaf up to date with the rest of the cluster.
To attach a leaf without rebalancing partitions, use the
For more information see REBALANCE PARTITIONS .
ATTACH LEAFcan only be run on leaf nodes that are present in
This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStore Commands ).
FORCEflag overrides any conflicts that would prevent
ATTACH LEAFfrom running.
In practice, this happens when the data on the leaf has diverged away from the current state of the cluster (for example, a database was recreated while the leaf was down). You do not need to
ATTACH LEAF .by default.
. . FORCE
ATTACH LEAFwithout the
FORCEflag collects information about which databases on the leaf are conflicting and the error message indicates directly that you should add the
By specifying the
FORCEflag, you enable
ATTACH LEAFto ignore the conflicting data on the node you are attaching.
FORCEflag does not drop the conflicting databases on the node, but you can remove orphaned database partitions on the leaf by running the
ATTACH LEAF FORCEcommand followed by the
CLEAR ORPHAN DATABASEScommand.
If you want to reattach many leaves at one time, after restarting a cluster, for example, you can use ATTACH LEAF ALL.
Detached leaves automatically reattach.
To disable this feature, set the global variable
For more information see SET GLOBAL .
This command causes implicit commits.
See COMMIT for more information.
See the Permission Matrix for the required permission.
ATTACH LEAF '192.168.1.110':3306;
Query OK, 1 row affected (1.11 sec)
Last modified: July 31, 2023