DETACH LEAF

Detaches a leaf.

Similar to REMOVE LEAF except that it keeps the leaf in the detached state instead of removing it entirely.

Syntax

DETACH LEAF 'host':port [KILL]

Remarks

  • 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.

  • 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.

Example

DETACH LEAF '192.168.1.110':3306;

DETACH LEAVES

Detaches all leaves.

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

Syntax

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

Remarks

  • 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.

Example

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

Last modified: January 9, 2025

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