ALTER CLUSTER DROP

Overview

Drops a failed node from the cluster and triggers a group change.

USAGE

DETAILS

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.

Note

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.

Only use ALTER CLUSTER DROP in the event of emergency.

To remove a node without risking data loss, use ALTER CLUSTER SOFTFAIL instead.

Removing Nodes

To remove a node:

  1. Connect to an Xpand node that is in the cluster.

  2. Execute the ALTER CLUSTER DROP statement to remove the node:

    ALTER CLUSTER DROP 4;
    

The Xpand Node and all replicas stored on it are no longer available to the cluster.

SYNONYMS

SCHEMA

PARAMETERS

SKYSQL

PRIVILEGES

EXAMPLES

ERROR HANDLING

FEATURE INTERACTION

RESPONSES

DIAGNOSIS

ISO 9075:2016

CHANGE HISTORY

Release Series

History

23.09

  • Present starting in MariaDB Xpand 23.09.1.

6.1

  • Present starting in MariaDB Xpand 6.1.0.

6.0

  • Present starting in MariaDB Xpand 6.0.3.

5.3

  • Present starting in MariaDB Xpand 5.3.13.

Release Series

History

6.0

  • Present starting in MariaDB Xpand 6.0.3.

5.3

  • Present starting in MariaDB Xpand 5.3.13.

Release Series

History

6.1

  • Present starting in MariaDB Xpand 6.1.0.

EXTERNAL REFERENCES