Sign inTry Free

Error Handling

On this page

This section lists errors that can occur when SingleStore processes the logs and the snapshots. It also discusses how SingleStore addresses the errors.

CRC32 Instruction not Supported

If your system hardware does not support the CRC32 instruction, you will receive the following error.

Warning: SSE4.2 is not supported. Resorting to software CRC32C. SingleStore recovery and log writing performance will be negatively impacted.

This error will be commonly seen on older processors and some virtualized environments. In this instance, SingleStore will use a software implementation of CRC32; however, this will slow down reading and writing log files. SingleStore recommends that production deployments of SingleStore run on environments that support this instruction.

Data Corruption Found During Replay

During replay, if SingleStore encounters corrupted logs or snapshots, it puts the database in the unrecoverablestate. Such a database will usually auto-heal if in High availability, Redundancy-2 mode and the corrupted logs or snapshots are on the replica partitions. During auto-healing, the primary host takes a snapshot and sends it to the replica. When auto-healing is complete, the secondary database will resume its operation in the replicating state.

Last modified: October 31, 2023

Was this article helpful?

On this page

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