Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

_SYNC_PLANS

The _SYNC_PLANS command synchronizes a node's local PPC with the DPC for a specific database.

_SYNC_PLANS <dbName>;

When this command is run on a node, it downloads up to distributed_plancache_max_download_plans from the DPC to that node's local PPC for the specified database.

The _SYNC_PLANS command first downloads one plan per table in the database. Query plans are downloaded only after these "table plans" are downloaded. For databases in which the number of tables in the database is close to the value of distributed_plancache_max_download_plans, SingleStore recommends increasing the value of distributed_plancache_max_download_plans to a value greater than the number of tables in the database before running the command.

When the _SYNC_PLANS command is run, a synchronization task will be added to the DPC task queue regardless of whether enable_distributed_plancache is set to ON or OFF. If the request is enqueued while enable_distributed_plancache is set to OFF, the task will run when enable_distributed_plancache is set to ON.

Refer to Distributed Plancache for more information.

Last modified:

Was this article helpful?

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In