Sign inTry Free

PROMOTE AGGREGATOR … TO MASTER

On this page

This command promotes a child aggregator node to master, while demoting the current master to child.

This is useful for host maintenance that requires a restart of the master aggregator, or replacement of the old master aggregator with new hardware.

Syntax

PROMOTE AGGREGATOR '<host>':<port> TO MASTER;

Arguments

  • <host> is the host of the child aggregator to be promoted.

  • <port> is the port of the child aggregator to be promoted.

Remarks

  • The node to be promoted must already be a child aggregator in the cluster and must currently be online.

  • enable_query_forwarding must be set to ON for DDL and DML queries to continue to run while PROMOTE AGGREGATOR executes. See Sync Variables Lists for more information on this variable.

  • If there is permanent loss of the master aggregator, use AGGREGATOR SET AS MASTER instead of PROMOTE AGGREGATOR ... TO MASTER.

  • This command can be run on a master or child aggregator node (see Node Requirements for SingleStore Commands).

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

  • Refer to the Permission Matrix for the required permission.

Permissions

The specified user account must have full permissions on the node to execute this command, namely the cluster privilege. For more information, see Permissions Matrix.

Example

PROMOTE AGGREGATOR '127.0.0.1':3307 TO MASTER;
Query OK, 0 rows affected (2.971 sec)

Related Topics

Last modified: November 29, 2024

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK