Sign inTry Free

Troubleshooting SingleStore Debezium Connector

On this page

Connector Unable to Start

When a connector is stopped for an extended period of time and fails to start, it returns the following exception:

Offset the connector is trying to resume from is considered stale...

This exception indicates that the offset the connector is trying to resume from is now stale and the connector cannot resume from this offset.

To recover from this failure, perform either of the following:

  • Delete the failed connector, and create a new connector with the same configuration but with a different connector name.

  • Pause the connector and then remove offsets or change the offset topic.

  • Run the connector in the when_needed snapshot mode. After starting in the when_needed mode, the connector automatically removes the stale offsets and performs a snapshot. Refer to snapshot.mode for related information.

To prevent failures caused by stale offsets, increase the value of the following engine variables:

  • snapshots_to_keep: Defines the number of snapshots to keep for backup and replication.

  • snapshot_trigger_size: Defines the size of transaction logs in bytes, which, when reached, triggers a snapshot that is written to disk.

Note

Increasing the values of these engine variables also leads to an increase in the memory consumption.

Last modified: March 31, 2025

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