Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.

Storage Location for Transaction Logs and Snapshots

The datadir engine variable stores the location of transaction logs and snapshots. Transaction logs are typically stored in the /var/lib/memsql/<node_ID>/data/logs directory with the log file names resembling the following format: metrics_3_log_v1_15335424. In this example,

  • metrics is the database name

  • 3 is the partition number

  • log is the file type

  • v1 is the file format version number

  • 15335424 is the log sequence number (LSN)

Snapshots are typically located in the /var/lib/memsql/<node_ID>/data/snapshots directory with the snapshot names resembling the following format: memsql_snapshot_v1_0_28. In this example,

  • memsql is the name of the source database

  • snapshot is the file type

  • v1 is the file format version number

  • the remaining characters represent the sequence number

Last modified: January 10, 2022

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