Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

MV_ACTIVE_DISTRIBUTED_TRANSACTIONS

This view shows internal information on distributed transactions that are currently active in the system.

Primarily for use by SingleStore Customer Support. No additional information about this view is available.

Column Name

Description

DISTRIBUTED_XACT_ID

The internal ID of the distributed transaction.

COORDINATOR_ID

ID of the aggregator coordinating the distributed transaction.

CONNECTION_ID

Internal connection ID between the node and the aggregator.

NODE_ID

ID of the node where the transaction is running.

DATABASE_NAME

The name of the database or partition running the transaction.

ISOLATION_LEVEL

The isolation level the distributed transaction is running on.

REAL_CLOCK_BEGIN_TIME_STAMP

Time of the start of the transaction.

START_TIME_STAMP

Internal timestamp of the start of the transaction.

READ_TIME_STAMP

Internal timestamp of the first data read from the transaction.

EXECUTION_STATE

The state of the transaction: idle, running, preparing, prepared, prepare_failed.

PREPARE_TIME_STAMP

The internal timestamp of when the local prepare step of the transaction was executed.

ROW_LOCKS

Number of rows locks held by the transaction.

Last modified:

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