SingleStore DB

information_schema.MV_EVENTS

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 table. The table is flushed upon database restart, but otherwise there is no set retention period.

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

Learn more about interpreting this view in the SingleStore DB 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

This section 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.

NODE_MEMORY_VIOLATION

The available memory for the related node has gone below the desired threshold. The engine variable node_memory_low_threshold_mb sets this threshold.

NODE_DISK_VIOLATION

A warning that available disk space has gone below the desired threshold. The engine variable node_disk_low_threshold_mb sets this threshold.

NODE_PING_VIOLATION

A warning that the network ping latency for a node has increased above the allowed threshold. See node_ping_latency_high_threshold_ms.

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.

MAX_BLOB_CACHE_SIZE_ON_REPLAY

This means that blob SingleStore ran out of cache space while attempting to create a blob, stopping replay.