HeatWave User Guide  /  System and Status Variables  /  Status Variables

9.2 Status Variables

Several status variables provide operational information about MySQL HeatWave. You can retrieve status data using SHOW STATUS syntax. For example:

mysql> SHOW STATUS LIKE 'hw_data_scanned';
+-----------------+-------+
| Variable_name   | Value |
+-----------------+-------+
| hw_data_scanned | 0     |
+-----------------+-------+

mysql> SHOW STATUS LIKE 'secondary%';
+----------------------------------+-------+
| Variable_name                    | Value |
+----------------------------------+-------+
| Secondary_engine_execution_count | 0     |
+----------------------------------+-------+

mysql> SHOW STATUS LIKE 'rapid%';
+---------------------------------+------------+
| Variable_name                   | Value      |
+---------------------------------+------------+
| 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     |
+---------------------------------+------------+
  • hw_data_scanned

    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.

    • 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.

    • OFF: Change propagation is not enabled.

  • rapid_cluster_status

    The MySQL HeatWave Cluster status.

    • ON: The MySQL HeatWave Cluster is enabled.

    • OFF: The MySQL HeatWave Cluster is not enabled.

  • rapid_core_count

    The MySQL HeatWave node core count. The value remains at 0 until all MySQL HeatWave nodes are started.

  • rapid_heap_usage

    MySQL DB System node heap usage.

  • rapid_lakehouse_automatic_incremental_load_health

    Available as of MySQL 9.4.1. The value of this variable is a JSON object containing two string fields: status and details. You can review the details field for a description of the status, such as a reason for a disabled status.

    The following statuses are available:

    • disabled: The event-based incremental load feature is not available. Review the details field for more information on the reason for the status.

    • initializing: The event-based incremental load feature is waiting for the server to finish booting and verifying which external tables are set up for event-based incremental loading.

    • online: The event-based incremental load feature is available. The details field states the number of unique streams that are set up for a specific number of tables. For example: Listening for n streams for x tables.

  • rapid_lakehouse_health

    • 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.

  • rapid_lakehouse_total_loaded_bytes

    Total bytes of all external tables loaded in MySQL HeatWave.

  • rapid_load_progress

    A percentage value indicating the status of a table load operation.

  • rapid_ml_operation_count

    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.

  • rapid_ml_status

    The status of MySQL HeatWave AutoML.

    • ON: MySQL HeatWave AutoML is available to use.

    • OFF: MySQL HeatWave AutoML is not available to use.

  • rapid_n_external_tables

    Returns the number of external tables. For example:

    +-------------------------+-------+
    | Variable_name           | Value |
    +-------------------------+-------+
    | rapid_n_external_tables | 2     |
    +-------------------------+-------+
  • rapid_plugin_bootstrapped

    The bootstrap mode for the MySQL HeatWave plugin.

    • YES: The MySQL HeatWave plugin is initialized and ready to use.

    • NO: The MySQL HeatWave plugin is installed, but it is not active.

    • IDLE: The MySQL HeatWave plugin is installed and the basic configuration is set. In this state, there is no connectivity to RAPID servers, MySQL HeatWave Cluster is not available, and change propagation is not running.

    • SUSPENDED: The MySQL HeatWave plugin is installed and the change propagation thread is started. The network is disabled and user operations cannot be offloaded to RAPID.

  • rapid_preload_stats_status

    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”.

  • rapid_query_offload_count

    The number of queries offloaded to MySQL HeatWave for processing.

  • rapid_service_status

    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.