Oracle Cloud Infrastructure Documentation

Managing a HeatWave Cluster

Starting, Stopping, or Restarting a HeatWave Cluster

You can start, stop, or restart a HeatWave cluster.

Note

In an Always Free DB system, you cannot start, stop, or restart a HeatWave cluster independent of the DB system. You can start, stop, or restart an Always Free DB system together with the HeatWave cluster.

Using the Console

Use the Console to start, stop, or restart a HeatWave cluster.

  1. Open the navigation menu, and select Databases. Under HeatWave MySQL, click DB systems.
  2. In the HeatWave cluster filter, select Attached to filter the DB systems that have a HeatWave cluster attached.
  3. Click the name of your DB system to open the DB system details page.
  4. In the Resources list, click HeatWave cluster.
  5. Select one of the following actions:
    • Start: Start a stopped HeatWave cluster. After the HeatWave cluster is started, the Stop action is enabled and the Start option is disabled.
    • Stop: Stop a running HeatWave cluster. After the HeatWave cluster is stopped, the Start action is enabled and the Stop option is disabled..
    • Restart: Shut down a HeatWave cluster, and restart it.
      Note

      When you stop a HeatWave cluster through a stop or restart action, the data loaded in HeatWave cluster memory is lost. When you start or restart a HeatWave cluster, HeatWave automatically reloads the data that was previously loaded using the HeatWave recovery mechanism as described in HeatWave Cluster Failure and Recovery. Data changes that occur on the DB system while the HeatWave cluster is offline are included in the reloaded data.

Editing a HeatWave Cluster

You can change the shape of a HeatWave cluster and resize the number of nodes in a HeatWave cluster.

Note

You cannot change the shape and size of a HeatWave cluster in an Always Free DB system.
  • Changing the shape: If you change the shape of a HeatWave cluster, you must reload the data to the HeatWave cluster.
  • Resizing the HeatWave cluster: You can increase or decrease the number of nodes of a HeatWave cluster.
    • Elastic resize happens when one of the following conditions is satisfied:
      • The database version is 8.2.0 or higher with HeatWave Lakehouse disabled.
      • The database version is 9.1.0 or higher with HeatWave Lakehouse enabled and the number of nodes before and after the resize is not more than 64.
      Note

      Elastic resize happens in real-time with no downtime or service disruption. During elastic resize, the HeatWave cluster remains available to process queries and keeps the loaded tables in memory. Resizing the nodes of a HeatWave cluster provides the following benefits:
      • Available: There is no downtime or service disruption during resize, and you can continue to run queries on the DB system.
      • Flexible: Based on the size of the data, you can increase or decrease the HeatWave cluster nodes to any number between 1 and 64. Also, you can estimate the number of nodes required based on the shape you selected and the size of the data. See Generating a Node Count Estimate.
      • Balanced: After resize completes, data is balanced across all nodes in the cluster, and any new queries are run in the new cluster size.
    • Otherwise, a normal resize occurs. The HeatWave cluster will be shut down and restarted. And, you must reload the data to the HeatWave cluster after the resize operation has completed.

Using the Console

You can use the Console to change the shape and resize the number of nodes of a HeatWave cluster

  1. Open the navigation menu and select Databases. Under HeatWave MySQL, click DB systems.
  2. In the HeatWave cluster filter, select Attached to filter the DB systems that have a HeatWave cluster attached.
  3. Click the name of the DB system to open the DB system details page.
  4. Do either of the following:
    • In the DB system information tab, under HeatWave cluster, besides the HeatWave cluster field, click Edit.
    • Under Resources, click HeatWave cluster, and then click Edit in the HeatWave cluster information frame.
  5. In the Edit HeatWave cluster panel, under Configure HeatWave cluster, do the following:
    1. Select a shape: Click Change shape, and select the shape of the HeatWave cluster, and click Select a shape.
    2. Node: Specify the number of nodes of a HeatWave cluster.
    3. Estimate node: (Optional) Click it to estimate the number of nodes required based on the shape you selected and the size of your data. See Generating a Node Count Estimate.
The HeatWave cluster enters the Updating state, and the HeatWave cluster is updated.

Deleting a HeatWave Cluster

You can permanently delete a HeatWave cluster from the DB system. Deleting the HeatWave cluster has no effect on the DB system to which the HeatWave cluster is attached. However, deleting the DB system deletes the attached HeatWave cluster.

Using the Console

Use the Console to delete a HeatWave cluster.

  1. Open the navigation menu and select Databases. Under HeatWave MySQL, click DB Systems.
  2. In the HeatWave cluster filter, select Attached to filter the DB systems that have a HeatWave cluster attached.
  3. Click the name of your DB system to open the DB system details page.
  4. In the Resources list, click HeatWave cluster.
  5. In the HeatWave cluster information frame, click Delete.
  6. On the Delete HeatWave cluster dialog box, click Delete HeatWave cluster.

Enabling or Disabling HeatWave Lakehouse

HeatWave Lakehouse enables query processing on the data residing in Object Storage. The source data is read from Object Storage, transformed to the HeatWave format, stored in the HeatWave cluster persistence storage layer, and then loaded to the HeatWave cluster memory.

HeatWave Lakehouse supports structured and relational data in CSV, Parquet, Avro, and JSON formats. Prior to MySQL 8.4.0, HeatWave Lakehouse is supported on the MySQL.HeatWave.VM.Standard and HeatWave.512GB shapes only. In MySQL version 8.4.0 or higher, HeatWave Lakehouse is supported on the MySQL.HeatWave.VM.Standard, HeatWave.512GB, HeatWave.32GB, and HeatWave.Free shapes.

Note

Prior to MySQL 8.3.0, you must disable point-in-time recovery, high availability, read replicas, and outbound replication in order to enable HeatWave Lakehouse.

Using the Console

Use the Console to enable or disable HeatWave Lakehouse.

  1. Open the navigation menu and select Databases. Under HeatWave MySQL, click DB systems.
  2. In the HeatWave cluster filter, select Attached to filter the DB systems that have a HeatWave cluster attached.
  3. Click the name of the DB system to open the DB system details page.
  4. To disable HeatWave Lakehouse, do the following:
    • Do either of the following:
      • In the DB system information tab, under HeatWave cluster, click Disable besides HeatWave Lakehouse.
      • Under Resources, click HeatWave cluster, and then click Disable besides HeatWave Lakehouse
    • In the Disable HeatWave Lakehouse dialog box, click Disable.
  5. To enable HeatWave Lakehouse, do the following:
    • Do either of the following:
      • In the DB system information tab, under HeatWave cluster, click Enable besides HeatWave Lakehouse.
      • Under Resources, click HeatWave cluster, and then click Enable besides HeatWave Lakehouse
    • In the Enable HeatWave Lakehouse dialog box, click Enable.
The HeatWave cluster enters the Updating state and HeatWave Lakehouse is enabled or disabled.