August 11, 2025

The Cloudera Operational Database 1.53 version supports vertical scaling and snapshot creation using the Cloudera Operational Database UI.

Vertical Scaling using the Cloudera Operational Database UI

The Cloudera Operational Database user interface facilitates vertical scaling based on the supported instance types for each node group separately.

A Vertical Scaling button has been incorporated into the Nodes tab within the Database Manager page. To initiate vertical scaling, an available instance type provided by a node group can be utilized. The quantity of instance types assigned to each node group is contingent upon the database's scale type, such as Micro, Light, or Heavy Duty.

To ascertain the supported instance types for a given combination of cloud platform, scale type, and storage type, the list-supported-instance-types CLI command can be employed. For more information, see Release Notes.

Enhancements to the drop database command

A new option --force is added to the CLI command, drop-database. You can use this option to forcibly drop the database.

The following is an example of the command using the --force option.

cdp opdb drop-database --environment-name [***ENVIRONMENT NAME ***] --database-name [***DATABASE NAME***] --force

For more information, see drop-database.

Snapshot creation using the Cloudera Operational Database UI

You can create a snapshot of an HBase table using the Cloudera Operational Database user interface.

Database table snapshots serve various purposes, including backup and recovery, reporting or analytical functions, and the preservation of regulatory or audit data. These snapshots can subsequently be restored from their designated location to an available target database.

To know more about the snapshot creation, see Working with snapshots in Cloudera Operational Database.

Enhancements to the update-hbase-configuration CLI command

The behavior of the following parameters in the update-hbase-configuration CLI command is modified:

  • The --configuration-value option is now an optional parameter.
  • Safety valve items can be added or updated using the --set-safety-valve-item-name and --set-safety-valve-item-value parameters.
  • Safety valve items can be removed using the --unset-safety-valve-item-name parameter.
  • Safety valve modifications do not reorder existing items; new items are appended to the end.
  • The command supports XML, property file, and environment variable safety valves.

For more information, see update-hbase-configuration.