Important
The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.
DETACH LEAF
On this page
Detaches a leaf.
Similar to REMOVE LEAF except that it keeps the leaf in the detached state instead of removing it entirely.
Syntax
DETACH LEAF 'host':port [KILL] [ENSURE_PARTITION_SAFETY]
Remarks
-
DETACH LEAFtransitions the leaf from theonlinestate to thedetachedstate. -
DETACH LEAFis useful if you would like to temporarily take down a leaf for repairs without erasing it from metadata. -
If MemSQL Ops is not enabled for manual cluster control, then a
REMOVE LEAFcan result in the leaf being added back without user intervention. -
ENSURE_prevents a leaf (or leaves) from being detached if it contains the last online instance of a partition.PARTITION_ SAFETY -
Use ATTACH LEAF to attach a leaf that is currently in a
detachedstate. -
This command causes implicit commits.
Refer to COMMIT for more information. -
See the Permission Matrix for the required permission.
Example
DETACH LEAF '192.168.1.110':3306;
DETACH LEAVES
Detaches all leaves.
Similar to REMOVE LEAVES, except it detaches all leaves instead of removing them.
Syntax
DETACH LEAVES ('host_1':port_1, ..., 'host_n':port_n) [ENSURE_PARTITION_SAFETY]
Remarks
-
DETACH LEAVEStransitions the leaves from anonlinestate to adetachedstate. -
Use ATTACH LEAF ALL to attach leaves that are in a
detachedstate. -
All leaves must be in the same availability group to
DETACH LEAVES. -
DETACH LEAVESis an all-or-nothing command: either all the leaves will be detached, or none of them will. -
ENSURE_prevents a leaf (or leaves) from being detached if it contains the last online instance of a partition.PARTITION_ SAFETY
Example
DETACH LEAVES ('192.168.1.110':8080, '192.168.1.111':8080, '192.168.1.112':8080);
Related Topics
Last modified: January 9, 2025