ATTACH LEAF
On this page
Attaches a detached leaf into the cluster, re-introducing its data (if possible).
Syntax
ATTACH LEAF 'host':port [FORCE] [NO REBALANCE]
Remarks
-
ATTACH LEAF
will transition the leaf from thedetached
state to theonline
state.ATTACH
is used to reintroduce a leaf back into the system.By default, ATTACH LEAF
also 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 NO REBALANCE
option.For more information see REBALANCE PARTITIONS . -
ATTACH LEAF
can only be run on leaf nodes that are present inSHOW_
.LEAVES -
This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStore Commands ).
-
The
FORCE
flag overrides any conflicts that would preventATTACH LEAF
from 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 LEAF
without theFORCE
flag collects information about which databases on the leaf are conflicting and the error message indicates directly that you should add theFORCE
flag.By specifying the FORCE
flag, you enableATTACH LEAF
to ignore the conflicting data on the node you are attaching.The FORCE
flag does not drop the conflicting databases on the node, but you can remove orphaned database partitions on the leaf by running theATTACH LEAF FORCE
command followed by theCLEAR ORPHAN DATABASES
command. -
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 auto_
toattach false
.For more information see SET GLOBAL . -
This command causes implicit commits.
Refer to COMMIT for more information. -
See the Permission Matrix for the required permission.
Example
ATTACH LEAF '192.168.1.110':3306;
Query OK, 1 row affected (1.11 sec)
Related Topics
Last modified: July 31, 2023