Sign inTry Free

Operations

On this page

Operations allows to manage and troubleshoot the data pipeline, control the synchronization process, and handle the schema changes. To manage the data ingestion pipeline, navigate to the Operations tab.

Select the following according to your requirements.

  1. Restore on Startup (On/Off toggle): Enable or disable to determine whether the pipeline must automatically restore its previous state when the system starts.

  2. Full Extract: Trigger the initial bulk load for all the selected tables, except those marked as Skip Initial Extract. Every Ingest pipeline must undergo a full extract at least once to begin with.

  3. Sync New Tables: Trigger the initial bulk load for tables marked as Redo Initial Extract and newly added tables in an ongoing replication. This operation cannot replace a full extract.

  4. Sync Struct: Compare and fix the table structure in the destination database. Load fails if the schema changes. The operator identifies when the load started failing and rolls back to a point just before the initial failure. During this operation, Ingest compares and updates the structure of the destination table without losing data. If a significant amount of time has passed or the log file is unavailable, triggers a Redo Initial Extract to sync the table.

  5. Rollback: Replay logs from a specific point to reapply changes to the destination. If the primary key columns are correctly selected, there should be no duplicates in the destination table. Rollback affects all tables in the selected list.

  6. Manual Delta : Triggers a manual delta extract to process incremental changes.

Rollback

In the event of unexpected issues, such as intermittent source database outages or network connectivity problems, you can rollback Ingest to a point in time before the issue occurred and replay the changes.

To perform the rollback:

  1. Navigate to the Schedule tab.

  2. Select Rollback.

  3. The rollback screen appears, displaying a list of available rollback points in descending order, depending on the source database log retention policy.

  4. Select the desired date (radio button) and Select.

  5. Select Rollback to initiate the rollback.

  6. Ingest automatically catches up from the selected point in time to the current time that replays all log entries and applies them to the destination.

Last modified: January 29, 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