SHOW FULLTEXT SERVICE STATUS

Shows the status of the full-text V2 service.

Syntax

SHOW FULLTEXT SERVICE STATUS;

Remarks

  • The full-text service typically does not run on aggregator nodes.

Examples

Here's sample output after the full-text service has shut down due to inactivity. The first 6 nodes are aggregators, which do not normally run the full-text service (thus the "NULL" message).

SHOW FULLTEXT SERVICE STATUS;
+---------+---------+-------------------------------+
| Node ID | State   | Message                       |
+---------+---------+-------------------------------+
|       1 | Stopped | NULL                          |
|      18 | Stopped | NULL                          |
|      19 | Stopped | NULL                          |
|      20 | Stopped | NULL                          |
|      21 | Stopped | NULL                          |
|      22 | Stopped | NULL                          |
|       2 | Stopped | Process exited with status 0. |
|       3 | Stopped | Process exited with status 0. |
|       4 | Stopped | Process exited with status 0. |
|       5 | Stopped | Process exited with status 0. |
|       6 | Stopped | Process exited with status 0. |
|       7 | Stopped | Process exited with status 0. |
|       8 | Stopped | Process exited with status 0. |
|       9 | Stopped | Process exited with status 0. |
|      10 | Stopped | Process exited with status 0. |
|      11 | Stopped | Process exited with status 0. |
|      12 | Stopped | Process exited with status 0. |
|      13 | Stopped | Process exited with status 0. |
|      14 | Stopped | Process exited with status 0. |
|      15 | Stopped | Process exited with status 0. |
|      16 | Stopped | Process exited with status 0. |
|      17 | Stopped | Process exited with status 0. |
+---------+---------+-------------------------------+

Here is the sample output while the full-text service is running. Again, the first 6 nodes are aggregators.

SHOW FULLTEXT SERVICE STATUS;
+---------+---------+---------+
| Node ID | State   | Message |
+---------+---------+---------+
|       1 | Stopped | NULL    |
|      18 | Stopped | NULL    |
|      19 | Stopped | NULL    |
|      20 | Stopped | NULL    |
|      21 | Stopped | NULL    |
|      22 | Stopped | NULL    |
|       2 | Running | Ready   |
|       3 | Running | Ready   |
|       4 | Running | Ready   |
|       5 | Running | Ready   |
|       6 | Running | Ready   |
|       7 | Running | Ready   |
|       8 | Running | Ready   |
|       9 | Running | Ready   |
|      10 | Running | Ready   |
|      11 | Running | Ready   |
|      12 | Running | Ready   |
|      13 | Running | Ready   |
|      14 | Running | Ready   |
|      15 | Running | Ready   |
|      16 | Running | Ready   |
|      17 | Running | Ready   |
+---------+---------+---------+

Last modified: August 27, 2024

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