Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.

MV_SEQUENCES

On this page

This view shows the status and statistics of all sequences in the system. It provides information about sequence ownership, current values, performance metrics, and cache statistics for both leaf nodes and aggregators. Refer to AUTO_INCREMENT AS SEQUENCE for related information.

Column Name

Description

NODE_ID

ID of the node to which the other columns in the view apply.

DATABASE_NAME

Name of the database that contains the table.

TABLE_NAME

Name of the table that contains the sequence column.

COLUMN_NAME

Name of the column defined as a sequence.

PARTITION_ID

ID of the partition that currently owns the sequence and coordinates unique values for all aggregators.

IS_OWNER_LEAF

Indicates whether this node is the leaf node that owns the partition and receives range requests from aggregators.

IS_AGGREGATOR

Indicates whether this node functions as an aggregator.

VALUE

Has different meanings depending on the node role:

  • Owner leaf: Start value of the next sequence range to serve.

  • Aggregator: Next sequence value to generate from the cached range.

LAST_ACCESS_TIME

Timestamp of the last range request from an aggregator. Applies only to the owner leaf.

CURRENT_RANGE

Size of the sequence range starting from VALUE. SingleStore adjusts this size based on load and the following variables: sequence_min_cache_count, sequence_max_cache_count, sequence_cache_resize_up_time_us, sequence_cache_resize_down_time_us. Refer to Configure Sequences for more information.

Applies to the owner leaf only.

FETCHES

Number of range requests sent by this aggregator to the owner leaf. Applies to aggregators only.

CACHE_MISSES

Number of times an aggregator required a new range because no valid cached range was available. High values indicate potential performance issues.

PRE_FETCHES

Number of successful pre-fetch operations performed by an aggregator before exhausting its current range.

DOUBLE_PREFETCHES

Number of times an aggregator attempted to pre-fetch while another fetch was already in progress. High values indicate heavy load and rapid cache exhaustion.

ERRORS

Number of errors encountered when requesting a new range from the owner leaf. High values may indicate cluster instability or network problems.

LMV_SEQUENCES

The LMV_SEQUENCES view provides the same information as MV_SEQUENCES but only for the local node. It excludes the NODE_ID column.

Use this view to inspect sequence behavior on the current node without querying cluster-wide data.

Last modified: February 18, 2026

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

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