Sign inTry Free

MV_EVENTS

On this page

This view contains information about events and is useful for monitoring events across clusters over time.

Information on the most recent 1028 events is stored in the view. The view is flushed upon database restart, but otherwise there is no set retention period.

Events from all nodes are stored in the view and when a node is restarted, events specific to that node are removed from the view. For example, if the Master Aggregator is restarted, events related to it are removed from the view, while events from other nodes will remain.

Learn more about interpreting this view in the Components to Monitor guide.

Column Name

Description

ORIGIN_NODE_ID

The ID of the node from where a given event occurred.

EVENT_TIME

The timestamp of a given event.

SEVERITY

The severity of a given event: NOTICE, WARNING, or ERROR

EVENT_TYPE

The type of event that occurred.

DETAILS

Additional information about a given event in JSON format.

MV_EVENTS.EVENT_TYPE

Provides descriptions for each potential result of SELECT DISTINCT EVENT_TYPE FROM information_schema.MV_EVENTS. Each result is one type of event occurring on the related node.

Event Type

Description

NODE_STARTING

The related node is starting up.

NODE_ONLINE

The related node is online.

NODE_OFFLINE

The related node is offline.

NODE_ATTACHING

The related node is attaching.

NODE_DETACHED

The related node is detaching.

LEAF_ADD

A leaf node is being added to the cluster.

LEAF_REMOVE

A leaf node is being removed from the cluster.

AGGREGATOR_ADD

An aggregator is being added to the cluster.

AGGREGATOR_REMOVE

An aggregator is being removed from the cluster.

DATABASE_REPLICATION_START

Replication of the database is started.

DATABASE_REPLICATION_STOP

Replication of the database is stopped.

REBALANCE_STARTED

REBALANCE_FINISHED

A partition rebalance has finished.

NOTIFY_AGGREGATOR_PROMOTED

The related node has been notified of an aggregator being promoted from child to master.

NODE_REACHABLE

The related node has become reachable.

NODE_UNREACHABLE

The related node has become unreachable.

SYSTEM_VAR_CHANGED

An engine variable was reconfigured.

HEARTBEAT_QUERY_FAILURE

A heartbeat query failed.

BACKUP_DB

The related database, and therefore the given node, has been backed up.

RESTORE_DB

A backup of the related database, and therefore the given node, has been restored.

MAX_MEMORY

Maximum server memory has been hit.

MAX_TABLE_MEMORY

Maximum table memory has been hit.

MAX_MEMORY_ON_REPLAY

This means that replicate operations ran out of memory, stopping replay.

PARTITION_UNRECOVERABLE

A partition is lost due to failure and no longer can be recovered.

WORKLOAD_THROTTLE

PIPELINE_STOPPED

A pipeline stopped.

INGEST_ERRORS_OUT_OF_DISK

Ingest is failing due to low disk space available.

DATABASE_REPROVISION

The related database is being reprovisioned.

Last modified: November 13, 2024

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