rpd_nodes table provides information
about HeatWave nodes.
rpd_nodes table has these columns:
A unique identifier for the HeatWave node.
The number of cores used by the HeatWave node.
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.
DRAMin MySQL 8.0.24)
The total memory in bytes allocated to the HeatWave node.
The base relation memory footprint per node.
The status of the HeatWave node. Possible statuses include:
The node is not operational.
IP address of the HeatWave node.
The port on which the HeatWave node was started.
The number of cluster events such as node down, node up, and so on.
GETrequests from the node to the object store.
The number of
PUTrequests from the node to the object store.
The number of
DELETErequests from the node to the object store.
HeatWave Machine Learning status. Possible status values include:
UNAVAIL_MLSTATE: HeatWave Machine Learning is not available.
AVAIL_MLSTATE: HeatWave Machine Learning is available.
DOWN_MLSTATE: HeatWave Machine Learning declares the node is down.
rpd_nodes table is read-only.
rpd_nodes 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
table until after the current recovery operation finishes and
the nodes that failed previously have rejoined the cluster.