ALTER CLUSTER DROP
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: SQL Statements for MariaDB Xpand
Topics on this page:
Drops a failed node from the cluster and triggers a group change.
See also: SQL Statements for MariaDB Xpand 6.1, in 6.0, and in 5.3
See also: SQL Statements for MariaDB Xpand 6.0 and in 5.3
See also: SQL Statements for MariaDB Xpand 6.1
ALTER CLUSTER DROP nodeid
This statement starts a group change to immediately remove an Xpand Node from the cluster. Xpand does not wait for the rebalancer process to move data off the node, which can leave your cluster vulnerable to data loss.
When a node is lost due to failure or
ALTER CLUSTER DROP, the rebalancer processor attempts in the background to replace the lost replicas from existing copies to reprotect the cluster. If another node fails during this process, it can result in partial availability.
ALTER CLUSTER DROP in the event of emergency.
To remove a node without risking data loss, use ALTER CLUSTER SOFTFAIL instead.
To remove a node:
Connect to an Xpand node that is in the cluster.
ALTER CLUSTER DROPstatement to remove the node:
ALTER CLUSTER DROP 4;
The Xpand Node and all replicas stored on it are no longer available to the cluster.