MySQL HeatWave User Guide
Several status variables provide operational information about
MySQL HeatWave. You can retrieve status data using
SHOW STATUS syntax. For example:
mysql> SHOW STATUS LIKE 'rapid%';
+---------------------------------+------------+
| Variable_name | Value |
+---------------------------------+------------+
| hw_data_scanned | 0 |
| rapid_change_propagation_status | ON |
| rapid_cluster_status | ON |
| rapid_core_count | 64 |
| rapid_heap_usage | 58720397 |
| rapid_load_progress | 100.000000 |
| rapid_ml_operation_count | 2 |
| rapid_ml_status | ON |
| rapid_plugin_bootstrapped | YES |
| rapid_preload_stats_status | Available |
| rapid_query_offload_count | 46 |
| rapid_service_status | ONLINE |
+---------------------------------+------------+
Tracks the amount of data scanned by successfully executed
MySQL HeatWave queries. Data is tracked in megabytes and is a
cumulative total of data scanned since the MySQL HeatWave Cluster was
last started. The counter is reset to 0 when the MySQL HeatWave Cluster
is restarted (when the
rapid_bootstrap state changes
from OFF or IDLE to
ON.)
rapid_change_propagation_status
The change propagation status.
A status of ON indicates that change
propagation is enabled globally, permitting changes to
InnoDB tables on the MySQL DB System to be
propagated to their counterpart tables in the MySQL HeatWave Cluster.
The MySQL HeatWave Cluster status.
The MySQL HeatWave node core count. The value remains at 0 until all MySQL HeatWave nodes are started.
MySQL DB System node heap usage.
A percentage value indicating the status of a table load operation.
A count of the number of MySQL HeatWave AutoML operations that a dbsystem executes. An operation typically includes multiple queries, and it increases for both successful and failed queries. It resets when a MySQL HeatWave node restarts.
The status of MySQL HeatWave AutoML. Possible values are
ON and OFF.
The bootstrap mode.
Reports the state of preload statistics collection.
Column-level statistics are collected for tables on the
MySQL DB System during a cluster size estimate. You can perform a
cluster estimate when adding or editing a MySQL HeatWave Cluster. States
include Not started, In
progress, and Statistics
collected.
Preload statistics are cached in the
rpd_preload_stats Performance Schema table.
See Section 8.1.7, “The rpd_preload_stats Table”.
The number of queries offloaded to MySQL HeatWave for processing.
Reports the status of the cluster as it is brought back online after a node failure.
Secondary_engine_execution_count
The number of queries executed by MySQL HeatWave. Execution occurs if query processing using the secondary engine advances past the preparation and optimization stages. The variable is incremented regardless of whether query execution is successful.
returns the following for two external tables loaded:
+-------------------------+-------+
| Variable_name | Value |
+-------------------------+-------+
| rapid_n_external_tables | 2 |
+-------------------------+-------+
rapid_lakehouse_total_loaded_bytes
Total bytes of all external tables loaded in MySQL HeatWave.
OFFLINE: Indicates an issue with the
RAPID storage engine.
RESOURCEPRINCIPALDOWN: The resource
principal token could not be retrieved.
RESOURCEPRINCIPALNOTSET: The resource
principal endpoint was not set.
LAKEHOUSEDISABLED: Lakehouse is not
currently enabled.
ONLINE: Lakehouse is enabled and
running.