8.1.6 The rpd_nodes Table

The rpd_nodes read-only table provides information about MySQL HeatWave nodes.

The table may not show the current status for a new node or newly configured node immediately. The rpd_nodes table is updated after the node has successfully joined the cluster.

If additional nodes fail while node recovery is in progress, the newly failed nodes are not detected and their status is not updated in the performance_schema.rpd_nodes table until after the current recovery operation finishes and the nodes that failed previously have rejoined the cluster.

The rpd_nodes table has the following columns:

• ID

  A unique identifier for the MySQL HeatWave node.

• CORES

  The number of cores used by the MySQL HeatWave node.

• MEMORY_USAGE

  Node memory usage in bytes. The value is refreshed every four seconds. If a query starts and finishes in the four seconds between refreshes, the memory used by the query is not accounted for in the reported value.

• MEMORY_TOTAL

  The total memory in bytes allocated to the MySQL HeatWave node.

• BASEREL_MEMORY_USAGE

  The base relation memory footprint per node.

• ML_MEMORY_STATE

  Available as of MySQL 9.4.0. The current ML_MEMORY_STATE of the node. The available statuses are IDLE, IDLE_CACHED, or ACTIVE. Updated about every five seconds, up to a maximum of every 11 seconds when ML_MEMORY_STATE is ACTIVE. Updated about every 60 seconds, up to a maximum of every 66 seconds when ML_MEMORY_STATE is IDLE, or IDLE_CACHED.

• ML_TOTAL_MEMORY_USAGE

  Available as of MySQL 9.4.0. The total amount of memory being used by the driver in bytes. Updated about every five seconds, up to a maximum of every 11 seconds when ML_MEMORY_STATE is ACTIVE. Updated about every 60 seconds, up to a maximum of every 66 seconds when ML_MEMORY_STATE is IDLE, or IDLE_CACHED.

• ML_MEMORY_TOTAL

  Available as of MySQL 9.4.0. The maximum amount of memory dedicated to the driver. Updated about every five seconds, up to a maximum of every 11 seconds when ML_MEMORY_STATE is ACTIVE. Updated about every 60 seconds, up to a maximum of every 66 seconds when ML_MEMORY_STATE is IDLE, or IDLE_CACHED.

• ML_MODEL_MEMORY_USAGE

  Available as of MySQL 9.4.0. The amount of memory used by the driver for all loaded models in bytes. Updated about every five seconds, up to a maximum of every 11 seconds when ML_MEMORY_STATE is ACTIVE. Updated about every 60 seconds, up to a maximum of every 66 seconds when ML_MEMORY_STATE is IDLE, or IDLE_CACHED.

• ML_MODEL_LOADED_COUNT

  Available as of MySQL 9.4.0. The number of currently loaded models. Updated about every five seconds, up to a maximum of every 11 seconds when ML_MEMORY_STATE is ACTIVE. Updated about every 60 seconds, up to a maximum of every 66 seconds when ML_MEMORY_STATE is IDLE, or IDLE_CACHED.

• STATUS

  The status of the MySQL HeatWave node. Possible statuses include:

  • NOTAVAIL_RNSTATE

    Not available.

  • AVAIL_RNSTATE

    Available.

  • DOWN_RNSTATE

    Down.

  • SPARE_RNSTATE

    Spare.

  • DEAD_RNSTATE

    The node is not operational.

• IP

  IP address of the MySQL HeatWave node.

• PORT

  The port on which the MySQL HeatWave node was started.

• CLUSTER_EVENT_NUM

  The number of cluster events such as node down, node up, and so on.

• NUM_OBJSTORE_GETS

  Number of GET requests from the node to the object store.

• NUM_OBJSTORE_PUTS

  The number of PUT requests from the node to the object store.

• NUM_OBJSTORE_DELETES

  The number of DELETE requests from the node to the object store.

• ML_STATUS

  MySQL HeatWave AutoML status. Possible status values include:

  • UNAVAIL_MLSTATE: MySQL HeatWave AutoML is not available.

  • AVAIL_MLSTATE: MySQL HeatWave AutoML is available.

  • DOWN_MLSTATE: MySQL HeatWave AutoML declares the node is down.