DETACH LEAF

Syntax

SQL

DETACH LEAF 'host':port [KILL][ENSURE_PARTITION_SAFETY]

DETACH LEAF transitions the leaf from the online state to the detached state.
DETACH LEAF is useful if you would like to temporarily take down a leaf for repairs without erasing it from metadata.
KILL prevents persistent long running write queries from blocking a clustering option for an arbitrarily long time (for example, a scale up or scale down or even an upgrade). Auto-rebalances automatically use the KILL mode if the auto-rebalance fails to run after three attempts.
ENSURE_PARTITION_SAFETY prohibits detaching a leaf (leaves) if it contains the last online instance of a partition. It is applicable for detaching multiple leaves.
Use ATTACH LEAF to attach a leaf that is currently in a detached state.
This command causes implicit commits. Refer to COMMIT for more information.
Node Requirements for SingleStore Commands
See the Permission Matrix for the required permission.

SQL

DETACH LEAF '192.168.1.110':3306;

Detaches all leaves.

Similar to REMOVE LEAVES, except it detaches all leaves instead of removing them.

SQL

DETACH LEAVES ('host_1':port_1, ..., 'host_n':port_n)

DETACH LEAVES transitions the leaves from an online state to a detached state.
Use ATTACH LEAF ALL to attach leaves that are in a detached state.
All leaves must be in the same availability group to DETACH LEAVES.
DETACH LEAVES is an all-or-nothing command: either all the leaves will be detached, or none of them will.

SQL

DETACH LEAVES ('192.168.1.110':8080, '192.168.1.111':8080, '192.168.1.112':8080);