Syntax

AGGREGATOR SET AS MASTER;

Remarks

• This command should only be used in cases where the master aggregator is permanently lost. The command PROMOTE AGGREGATOR … TO MASTER is required for all other use cases that require the promotion of a child aggregator to master.

• This command must be run on the child aggregator node to be promoted to master (see Node Requirements for SingleStore Commands ). If this command is run while your cluster has an online master aggregator, it will return an error.

• For version 7.1 and older, see Previous Versions.

• This command causes implicit commits. Refer to COMMIT for more information.

• See the Permission Matrix for the required permission.

Example

AGGREGATOR SET AS MASTER;

Query OK, 1 row affected (1 min 22.41 sec)

Related Topics

• Aggregator

• PROMOTE AGGREGATOR … TO MASTER

Previous Versions

In previous versions of SingleStore, AGGREGATOR SET AS MASTER required the following procedure:

1. Stop any DDL queries and writes to reference tables.

2. Confirm that the cluster and reference databases (if any) are in sync between the master aggregator and child aggregator to be promoted. To check the position of databases, create a connection to the MemSQL node and run the SHOW DATABASES EXTENDED command.

3. Disable detection of leaf failures and trigger failovers on the child aggregator. Set leaf_failure_detection variable on the target child aggregator to off. Perform this step from the master aggregator. If the current master aggregator is unresponsive, skip this step.

4. Stop the master aggregator using the memsql-ops memsql-stop <master_aggregator_ID> or sdb-admin stop-node --memsql-id <master_aggregator_ID> command. Make sure the master aggregator is offline before proceeding.

5. Clear the DNS cache on all the nodes in the cluster using the FLUSH HOSTS command.

6. Promote the child aggregator to the master aggregator. Run the AGGREGATOR SET AS MASTER command on the target child aggregator. Execute the SELECT @@master_aggregator query. This query should return self.

7. Enable leaf failure detection on the master aggregator. Set leaf_failure_detection variable to ON.

8. Remove the old master aggregator from the cluster using REMOVE AGGREGATOR.

9. Delete the old master aggregator. Run the memsql-ops memsql-delete <node_ID> or sdb-admin delete-node <node_ID> command.