Addressing Orphans by Attaching New Partitions

Look at the results of SHOW CLUSTER STATUS and SHOW PARTITIONS from the previous section. We are missing a master for partition 1, but we have an online orphan for partition 1. Assuming this orphan contains data we need, we will want to attach the master:

ATTACH PARTITION x_test:1 on '127.0.0.1':10002;
SHOW CLUSTER STATUS;
+-----------+-------+----------+-----------+-------------+----------+---------+
| Host      | Port  | Database | Role      | State       | Position | Details |
+-----------+-------+----------+-----------+-------------+----------+---------+
| 127.0.0.1 | 10001 | x_test   | Reference | replicating | 0:57     |         |
| 127.0.0.1 | 10001 | x_test_0 | Master    | online      | 0:10     |         |
| 127.0.0.1 | 10001 | x_test_1 | Replica   | replicating | 0:10     |         |
| 127.0.0.1 | 10002 | x_test   | Reference | replicating | 0:57     |         |
| 127.0.0.1 | 10002 | x_test_0 | Replica   | replicating | 0:10     |         |
| 127.0.0.1 | 10002 | x_test_1 | Master    | online      | 0:10     |         |
+-----------+-------+----------+-----------+-------------+----------+---------+
SHOW PARTITIONS;
+---------+-----------+-------+---------+--------+
| Ordinal | Host      | Port  | Role    | Locked |
+---------+-----------+-------+---------+--------+
| 0       | 127.0.0.1 | 10001 | Master  | 0      |
| 0       | 127.0.0.1 | 10002 | Replica | 0      |
| 1       | 127.0.0.1 | 10001 | replica | 0      |
| 1       | 127.0.0.1 | 10002 | Master  | 0      |
+---------+-----------+-------+---------+--------+

Warning

Do not run high level commands (REBALANCE PARTITIONS, RESTORE REDUNDANCY, DETACH LEAF, etc.) to attach the orphan into the cluster. High level commands may drop the orphan.

If your cluster has many partitions, you may want to count its partitions by role to help identify any orphaned partitions.

Last modified: April 27, 2023

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