Transaction Logs and Snapshots

Each partition on a node has a set of transaction logs that contain database updates made by DDL and DML commands. A snapshot is a database backup that contains only the in-memory rowstore data (of committed transactions). A snapshot is triggered each time the size of transaction logs reaches a predefined threshold. Snapshots can also be triggered manually for individual databases.

Transaction logs that are committed to snapshots are truncated to save disk space. In addition, old snapshots can be periodically deleted by configuring engine variables. At any given point, only transaction logs that are currently used by snapshots are stored on the disk.

Note that transaction logs are not stored in a human-readable format, unlike query log that is a text file.

The following sections provide general information about transaction logs and snapshots and further explain how to configure and manage the disk space used by them.

In this section

Last modified: November 17, 2022

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.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
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.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

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