# MV\_EVENTS

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

Information on the most recent 1,028 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.

| Column Name      | Description                                                 |
| ---------------- | ----------------------------------------------------------- |
| `ORIGIN_NODE_ID` | The`ID`of the node from which 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                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `AGGREGATOR_ADD`                         | An aggregator is being added to theworkspace.                                                                                                                                                                                                                                                                                                                                                                                                   |
| `AGGREGATOR_REMOVE`                      | An aggregator is being removed from theworkspace.                                                                                                                                                                                                                                                                                                                                                                                               |
| `ALTER_NODE_SET_HOST_PORT`               | Logged when aworkspacenode's hostname or port is changed via the`ALTER NODE`command.This tracks changes to node network configuration in theworkspacetopology.                                                                                                                                                                                                                                                                                  |
| `ASYNC_UPGRADE_FINISHED`                 | Marks the end of an asynchronous upgrade on aworkspace.                                                                                                                                                                                                                                                                                                                                                                                         |
| `ASYNC_UPGRADE_STARTED`                  | Marks the start of an asynchronous upgrade on aworkspace.                                                                                                                                                                                                                                                                                                                                                                                       |
| `ASYNC_UPGRADE_STEP_FINISHED`            | Marks the end of a specific asynchronous upgrade step on aworkspace.                                                                                                                                                                                                                                                                                                                                                                            |
| `ASYNC_UPGRADE_STEP_STARTED`             | Marks the start of a specific asynchronous upgrade step on aworkspace.                                                                                                                                                                                                                                                                                                                                                                          |
| `BACKUP_DB`                              | The related database, and therefore the given node, has been backed up.                                                                                                                                                                                                                                                                                                                                                                         |
| `BLOBCACHE_DISK_OK`                      | The previous cause of the`BLOBCACHE_LOW_DISK`event no longer applies, whereSingleStoreis now above the "redline" for disk usage.                                                                                                                                                                                                                                                                                                                |
| `BLOBCACHE_LOW_DISK`                     | The blob cache on a node is at or near its disk usage limit.                                                                                                                                                                                                                                                                                                                                                                                    |
| `BOTTLE_SERVICE_DOWN`                    | The Bottle Service has transitioned from an "up" state to a "down" state due to a detected heartbeat failure.                                                                                                                                                                                                                                                                                                                                   |
| `BOTTLE_SERVICE_ERROR`                   | There is an error in the Bottle Service.                                                                                                                                                                                                                                                                                                                                                                                                        |
| `BOTTLE_SERVICE_UP`                      | The Bottle Service has successfully transitioned from a "down" state to an "up" state. This occurs when a successful heartbeat is detected after one or more consecutive failures or during the first successful heartbeat after initialization.                                                                                                                                                                                                |
| `BOTTLE_SERVICE_WRONG_TERM`              | The Bottle Service detected an unexpected or mismatched "term" value—potentially connected to leader election, replication, or consensus protocol irregularities.                                                                                                                                                                                                                                                                               |
| `BOTTOMLESS_ALTER_COMPUTE`               | An even triggered by a periodic background task involved in bottomless storage management and, where supported, migration to the Bottle Service.                                                                                                                                                                                                                                                                                                |
| `BOTTOMLESS_INGEST_THROTTLED`            | Incoming writes have been slowed or halted because the system is unable to offload data to remote storage fast enough, or local resources (disk and cache) are threatened. This throttling is necessary to maintainworkspacestability and data durability, but is a signal that ingest configuration or resource provisioning may need optimization.                                                                                            |
| `BOTTOMLESS_RATE_LIMITED`                | The system has activated rate limiting for API calls to the bottomless storage system due to excessive requests or throttling signals. It provides details about the affected database and the number of slowdown exceptions encountered.                                                                                                                                                                                                       |
| `BOTTOMLESS_STORAGE_LOCKED_BY_OTHER`     | Operations involving the database's remote storage cannot proceed because a required lock is being held by another session—frequently arising after PITR or when certain processes are not properly cleaned up.                                                                                                                                                                                                                                 |
| `BOTTOMLESS_UPLOAD_DELAYED`              | Triggered when the system detects that uploads (of log chunks and blobs) are taking longer than expected. It provides details about the delay, including the affected database and the duration of the delay.                                                                                                                                                                                                                                   |
| `BOTTOMLESS_UPLOAD_VERIFICATION_FAILURE` | A failure occurred during the verification step of an upload to bottomless storage.                                                                                                                                                                                                                                                                                                                                                             |
| `CONSENSUS_ELECTION`                     | A consensus election has been started by this node. It has no keys.                                                                                                                                                                                                                                                                                                                                                                             |
| `CONSENSUS_ROLE_TRANSITION`              | A role transition has happened on this node (for example, voting member → demoted voting member), and has the following keys:<ul> <li>Previous_role - the previous role the node had</li> <li>New_role - the new role the node has</li> <li>Reason - description of why there was a transition</li> </ul>                                                                                                                                       |
| `CONSENSUS_STATE_TRANSITION`             | Represents changes to a node's state in the distributed consensus protocol (e.g., leadership elections, failovers). It provides the prior and new state, as well as the reason for transition.                                                                                                                                                                                                                                                  |
| `CONSENSUS_VOTING_REQUEST_RECEIVED`      | A voting request has been received by this node. It has the following keys:<ul> <li>Node_id - ID of the node that sent the vote request</li> <li>Last_log_index / last_log_term / term - details of the vote request</li> </ul>                                                                                                                                                                                                                 |
| `CONSENSUS_VOTING_REQUEST_SENT`          | This node has sent a vote request. It has the following keys:<ul> <li>Node_id - ID of the node to which the vote request was sent</li> <li>Last_log_index / last_log_term / term - details of the vote request</li> </ul>                                                                                                                                                                                                                       |
| `CONSENSUS_VOTING_RESPONSE_RECEIVED`     | This node has received a vote response to a request it sent. It has the following keys:<ul> <li>Node_id - ID of the node that sent the vote response</li> <li>Term - term of the vote request</li> <li>Vote - whether the voter voted yes or no</li> </ul>                                                                                                                                                                                      |
| `CONSENSUS_VOTING_RESPONSE_SENT`         | This node has responded to a voting request that it received. It has the following keys:<ul> <li>Node_id - ID of the node that sent the request referenced by this response</li> <li>Term - term of the vote request</li> <li>Vote - whether the voter voted yes or no</li> </ul>                                                                                                                                                               |
| `DATABASE_ATTACH_FINISH`                 | Marks the end of a database attach operation.The database has been attached and is accessible.                                                                                                                                                                                                                                                                                                                                                  |
| `DATABASE_ATTACH_START`                  | Marks the start of a database attach operation.The system has started attaching an existing database to theworkspace.                                                                                                                                                                                                                                                                                                                           |
| `DATABASE_CREATE_FINISH`                 | Marks the end of a database creation operation.The database has been created and is ready for use.                                                                                                                                                                                                                                                                                                                                              |
| `DATABASE_CREATE_START`                  | Marks the start of a database creation operation.The system has started processing the creation of a new database.                                                                                                                                                                                                                                                                                                                              |
| `DATABASE_DETACH_FINISH`                 | Marks the end of a database detach operation.The database has been detached and is no longer accessible.                                                                                                                                                                                                                                                                                                                                        |
| `DATABASE_DETACH_START`                  | Marks the start of a database detach operation.The system has started detaching a database from theworkspace.                                                                                                                                                                                                                                                                                                                                   |
| `DATABASE_DROP_FINISH`                   | Marks the end of a database drop operation.The database has been removed from the system.                                                                                                                                                                                                                                                                                                                                                       |
| `DATABASE_DROP_START`                    | Marks the start of a database drop operation.The system has started removing the database.Logged at the beginning of a database drop operation on the Master Aggregator. Includes the database name and drop action type (e.g., regular drop, drop unrecoverable, etc.). This is paired with`DATABASE_DROP_FINISH`to track the full lifecycle of the drop operation.                                                                            |
| `DATABASE_REPLICATION_START`             | Replication of the database has started.                                                                                                                                                                                                                                                                                                                                                                                                        |
| `DATABASE_REPLICATION_STOP`              | Replication of the database has stopped.                                                                                                                                                                                                                                                                                                                                                                                                        |
| `DATABASE_REPROVISION`                   | The related database is being reprovisioned.                                                                                                                                                                                                                                                                                                                                                                                                    |
| `HEARTBEAT_QUERY_FAILURE`                | A heartbeat query failed.                                                                                                                                                                                                                                                                                                                                                                                                                       |
| `INGEST_ERRORS_OUT_OF_DISK`              | Ingest is failing due to low available disk space.                                                                                                                                                                                                                                                                                                                                                                                              |
| `LEAF_ADD`                               | A leaf node is being added to theworkspace.                                                                                                                                                                                                                                                                                                                                                                                                     |
| `LEAF_REMOVE`                            | A leaf node is being removed from theworkspace.                                                                                                                                                                                                                                                                                                                                                                                                 |
| `LOW_DISK_SPACE`                         | SingleStoreran out of cache space while attempting to create a blob, stopping replay.                                                                                                                                                                                                                                                                                                                                                           |
| `MAX_BLOB_CACHE_SIZE_ON_REPLAY`          | SingleStoreran out of cache space while attempting to create a blob, stopping replay.                                                                                                                                                                                                                                                                                                                                                           |
| `MAX_MEMORY`                             | Maximum server memory has been reached.                                                                                                                                                                                                                                                                                                                                                                                                         |
| `MAX_MEMORY_ON_REPLAY`                   | A node has run out of available memory specifically during a "replay" operation.Replay refers to processes where the system must load, reconstruct, or reapply database state from persisted logs or snapshots. This can typically happen during database attach, restore, or node startup.                                                                                                                                                     |
| `MAX_TABLE_MEMORY`                       | Maximum table memory has been reached.                                                                                                                                                                                                                                                                                                                                                                                                          |
| `NEW_MASTER_AGGREGATOR`                  | A new Master Aggregator has been elected.Will also be issued when[AGGREGATOR SET AS MASTER](https://docs.singlestore.com/cloud/reference/sql-reference/workspace-management-commands/#aggregator-set-as-master.md)is used to forcibly change the MA).Each node in theworkspacewill issue this event when it learns of the election.It has the following keys:<ul> <li>Node_id - ID of the new MA</li> <li>Term - term for the new MA</li> </ul> |
| `NODE_ATTACHING`                         | The related node is attaching.                                                                                                                                                                                                                                                                                                                                                                                                                  |
| `NODE_DETACHED`                          | The related node is detaching.                                                                                                                                                                                                                                                                                                                                                                                                                  |
| `NODE_DISK_VIOLATION`                    | A node has encountered a disk-related error or has exceeded a disk usage threshold.This can potentially result in error conditions, warnings, or operational limitations for the node.                                                                                                                                                                                                                                                          |
| `NODE_MEMORY_VIOLATION`                  | A node has encountered a memory-related error or has exceeded a memory usage threshold.This can potentially result in error conditions, warnings, or operational limitations for the node.                                                                                                                                                                                                                                                      |
| `NODE_OFFLINE`                           | The related node is offline.                                                                                                                                                                                                                                                                                                                                                                                                                    |
| `NODE_ONLINE`                            | The related node is online.                                                                                                                                                                                                                                                                                                                                                                                                                     |
| `NODE_PING_VIOLATION`                    | Node failed to respond to a ping / heartbeat check within the expected timeframe.This can potentially indicate a connectivity or health issue.                                                                                                                                                                                                                                                                                                  |
| `NODE_REACHABLE`                         | The related node has become reachable.                                                                                                                                                                                                                                                                                                                                                                                                          |
| `NODE_STARTING`                          | The related node is starting up.                                                                                                                                                                                                                                                                                                                                                                                                                |
| `NODE_UNREACHABLE`                       | The related node has become unreachable.                                                                                                                                                                                                                                                                                                                                                                                                        |
| `NOTIFY_AGGREGATOR_PROMOTED`             | The related node has been notified of an aggregator being promoted from child to master.                                                                                                                                                                                                                                                                                                                                                        |
| `PARTITION_UNRECOVERABLE`                | A partition is lost due to failure and can no longer be recovered.                                                                                                                                                                                                                                                                                                                                                                              |
| `PIPELINE_STOPPED`                       | A pipeline stopped.                                                                                                                                                                                                                                                                                                                                                                                                                             |
| `REBALANCE_FINISHED`                     | A partition rebalance has finished.                                                                                                                                                                                                                                                                                                                                                                                                             |
| `REBALANCE_STARTED`                      | The rebalance process—which redistributes data partitions to optimize resource usage, recover from failures, or adjust for topology changes—began.                                                                                                                                                                                                                                                                                              |
| `REPAIR_JOB_STALLED`                     | A "repair job"—a background process responsible for maintaining data consistency, integrity, or recoverability—has stalled, which means it is taking longer to progress than expected.                                                                                                                                                                                                                                                          |
| `RESTORE_DB`                             | A backup of the related database, and therefore the given node, has been restored.                                                                                                                                                                                                                                                                                                                                                              |
| `SYSTEM_VAR_CHANGED`                     | An engine variable was reconfigured.                                                                                                                                                                                                                                                                                                                                                                                                            |
| `WORKLOAD_THROTTLE`                      | Event emitted when write workload throttling starts or stops because a sync replica’s replay falls behind.                                                                                                                                                                                                                                                                                                                                      |

***

Modified at: April 15, 2026

Source: [/cloud/reference/information-schema-reference/workspace-component/mv-events/](https://docs.singlestore.com/cloud/reference/information-schema-reference/workspace-component/mv-events/)

(An index of the documentation is available at /llms.txt)