MV_
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.
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.
Learn more about interpreting this view in the Components to Monitor guide.
|
Column Name |
Description |
|---|---|
|
|
The |
|
|
The timestamp of a given event. |
|
|
The severity of a given event: |
|
|
The type of event that occurred. |
|
|
Additional information about a given event in JSON format. |
MV_
Provides descriptions for each potential result of SELECT DISTINCT EVENT_.
|
Event Type |
Description |
|---|---|
|
|
The related node is starting up. |
|
|
The related node is online. |
|
|
The related node is offline. |
|
|
The related node is attaching. |
|
|
The related node is detaching. |
|
|
A leaf node is being added to the cluster. |
|
|
A leaf node is being removed from the cluster. |
|
|
An aggregator is being added to the cluster. |
|
|
An aggregator is being removed from the cluster. |
|
|
Replication of the database is started. |
|
|
Replication of the database is stopped. |
|
|
|
|
|
A partition rebalance has finished. |
|
|
The related node has been notified of an aggregator being promoted from child to master. |
|
|
The related node has become reachable. |
|
|
The related node has become unreachable. |
|
|
An engine variable was reconfigured. |
|
|
A heartbeat query failed. |
|
|
The related database, and therefore the given node, has been backed up. |
|
|
A backup of the related database, and therefore the given node, has been restored. |
|
|
Maximum server memory has been hit. |
|
|
Maximum table memory has been hit. |
|
|
This means that replicate operations ran out of memory, stopping replay. |
|
|
A partition is lost due to failure and no longer can be recovered. |
|
|
|
|
|
A pipeline stopped. |
|
|
Ingest is failing due to low disk space available. |
|
|
The related database is being reprovisioned. |
|
|
This means that SingleStore ran out of cache space while attempting to create a blob, stopping replay. |
Last modified: November 13, 2024