The feature to scale up the HBase REST server using the Apache HBase REST API is no longer a technical preview and is now generally available (GA).   For more information, see HBase REST server scaling in COD. This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

A new CLI option --switch-instance-type is added to the update-database command to switch the instance types to custom instance types for the COD clusters after the database creation. You must have the COD_USE_CUSTOM_INSTANCE_TYPES entitlement to use this option.   If you plan to scale up the cluster vertically or change the existing instance type to any custom instance type, you can use the --switch-instance-type option. However, the custom instance types must be included in the allowlist by the Cloudera Operational Database. Use the list-supported-instance-types command to fetch the list of supported instance types.   Following is an example of the usage.   cdp opdb update-database --environment-name <env_name> --database-name <database_name> --switch-instance-type instanceGroup=INSTANCEGROUP,instanceType=instancetype  For more information, see CDP CLI documentation. This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Cloudera Operational Database UI provides two new UI options Configure Database and Configure Edge Nodes to configure the worker and edge node properties in your existing operational database. You can access these menu items using the Actions menu item inside the database details page. For more information, see Configuring a database.  This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Cloudera Operational Database adds a new CLI command, list-supported-instance-types, allowing you to list the supported instance types for a combination of cloud platform, scale type, and storage type. You can filter using the instance group and architecture as well.   The --custom-instance-types option in the create-database command allows you to pick and choose instance types for the COD. However, it is essential that these instance types are included in the COD allowlist. The list-supported-instance-types command is useful to fetch the list of supported instance types.   Following is an example of the command.   cdp opdb list-supported-instance-types --cloud-platform AZURE --storage-type CLOUD_WITH_EPHEMERAL --scale-type MICRO --instance-group WORKER --architecture X86_64 For more information, see CDP CLI documentation. This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

When you create an operational database with HDFS storage type in an AWS environment, the Operational Database on HDFS clusters now also supports m6i and m7i instances for the applicable nodes. The Operational Database clusters with HDFS storage type are upgraded to enhance the operational database's performance and usability. The following are the new custom instance types supported by the Operational Database. AWS, HEAVY, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Master: m6i.8xlarge, m7i.8xlarge Compute/edge/leader: m6i.2xlarge, m7i.2xlarge Gateway: r6i.8xlarge, r7i.8xlarge AWS, LIGHT, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Compute/edge/leader/gateway: m6i.2xlarge, m7i.2xlarge Master: m6i.4xlarge, m7i.4xlarge This is available starting in COD v1.45 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

The Cloudera Operational Database CDP CLI adds a new option --custom-instance-types to the create-database command. Using this option, you can define custom instance types; however, the instance types must be included in the allowlist by the Operational Database. Currently, the allowlist is not accessible, however, the following are the new custom instance types supported by the Operational Database. AWS, HEAVY, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Master: m6i.8xlarge, m7i.8xlarge Compute/edge/leader: m6i.2xlarge, m7i.2xlarge Gateway: r6i.8xlarge, r7i.8xlarge AWS, LIGHT, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Compute/edge/leader/gateway: m6i.2xlarge, m7i.2xlarge Master: m6i.4xlarge, m7i.4xlarge The following is a sample output of the create-database command highlighting the usage of the --custom-instance-types option. cdp opdb create-database --environment-name cod_env --database-name cod_db --custom-instance-types masterType=m7i.4xlarge,workerType=m7i.4xlarge,leaderType=m7i.2xlarge,gatewayType=m7i.2xlarge --storage-type=HDFS --scale-type LIGHT The --storage-type option is now optional. If you do not define the --storage-type option, the Operational Database considers the default storage type. The default storage type is blob storage. If the ephemeral storage is enabled, the Operational Database considers the storage type CLOUD_WITH_EPHEMERAL; otherwise, CLOUD is considered. For more information, see CDP CLI documentation. This is available starting in COD v1.45 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

In CDP CLI, while creating an operational database, you can specify the encryption key to encrypt the volume for instance groups using the --volume-encryptions (array) option. You can select this option only in AWS environments. Following is a sample command. opdb create-database --environment-name <environment-name> --database-name <database-name> --disable-external-db --scale-type MICRO --attached-storage-for-workers '{"volumeCount":1,"volumeType":"SSD","volumeSize":100}' --endpoint-url http://localhost:8988 \ --volume-encryptions '[ { "encryptionKey": "<aws-key-arn>", "instanceGroup": "GATEWAY" } ]' Shorthand syntax: encryptionKey=string,instanceGroup=string ... (separate items with spaces) JSON syntax: [ { "encryptionKey": "string", "instanceGroup": "WORKER"|"LEADER"|"MASTER"|"GATEWAY"|"STRONGMETA"|"EDGE" } ... ] For more information, see CDP CLI documentation. This is available starting in COD v1.41 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

When you create and deploy an operational database in an Azure environment, by default, COD clusters now use Standard_D8s_v3 instance type instead of Standard_D8_v3. The instance type is upgraded to support encryption at the host level. If you want to retain the Standard_D8_v3 instance type, you must have the COD_USE_DV3_INSTANCE_TYPE entitlement on your account. This is available starting in COD v1.41 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

In CDP CLI, while creating an operational database, you can set the default root volume size with the --root-volume-size (integer) option in GiB for all the instances in the cluster. Following is a sample command. cdp opdb create-database --environment-name test-env --database-name test-db --root-volume-size 300 For more information, see CDP CLI documentation. This is available starting in COD v1.41 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

When you create an operational database with HDFS storage type, the COD clusters now use 16 core instances on AWS, Azure, and GCP environments for worker nodes. The COD clusters with HDFS storage type are upgraded to enhance the performance and usability of the COD. The new worker instances for HDFS storage type are as follows: AWS: m5.4xlarge Azure: Standard_D16_v3 GCP: n2-standard-16 This is available starting in COD v1.41 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more