Fixed issues

COD-4463 (Cloudera Operational Database 1.49) : Cloudera Operational Database autoscaling removes all nodes at once if workers are resized on the DataHub screen🔗

The Cloudera Operational Database autoscaling functionality is updated to limit the removal of nodes to a maximum of two at a time during cluster downscaling in specific scenarios. This change ensures that HDFS has sufficient time to relocate blocks, thereby preventing accidental data loss.

COD-3836 (Cloudera Operational Database 1.41) : Cloudera Operational Database supports deployments to specific subnets in Azure and GCP environments🔗

When you create an operational database using the CDP CLI, the subnet-id parameter in the create-database command is fixed and can be used to deploy the cluster into specific subnets in Azure and GCP environments.

Following is an example of subnet-id.

cdp opdb create-database --environment-name <env> --database-name <db> --subnet-id DataLakeHubSubnet1

For more information, see CDP CLI documentation.

ODX-2928 (Cloudera Operational Database 1.31) : Minor upgrade is not available🔗

Minor upgrades are available now while using the describe-upgrade-database CDP CLI command. You can now list the available hotfix versions using the describe-upgrade-database CDP CLI command.

ODX-1716 (Cloudera Operational Database 1.21) : Increase storage density for HDFS form factor🔗

Storage density for HDFS form factor is increased. Now, Cloudera Operational Database deploys 8 TB of disks for each worker instead of 6 TB during any new HDFS deployment.

ODX-1811 (Cloudera Operational Database 1.21) : Increase handler count🔗

The number of RegionServer handlers is increased to process 50% more read or write requests.