What's new in Cloudera Runtime 7.1.9

Open Data Lakehouse, powered by Apache Iceberg

CDP Private Cloud Base 7.1.9 delivers the hybrid Open Data Lakehouse providing the following benefits:

Open architecture: Cloudera’s Open Data Lakehouse, powered by Apache Iceberg is 100% open—open source, open standards based, and with wide community adoption. It can store multiple data formats and enables multiple engines to work on the same data.
Ease of adoption: By integrating Iceberg right into the Shared Data Experience (SDX) and Apache Ozone, Cloudera offers the easiest path to deploying a lakehouse. Additional capabilities like schema evolution, hidden partition, and more simplify data management for large datasets.
Multi-cloud: Build a lakehouse in your own data center and run anywhere. Cloudera offers the same data services with complete portability on all clouds.
Secure and governed: Iceberg tables integrate within SDX, allowing for unified security, fine-grained policies, governance, lineage and metadata management across multiple clouds, so you can focus on analyzing your data while Cloudera takes care of the rest.

For more information, see What is Open Data Lakehouse in CDP Private Cloud Base?

Apache Ozone

Ozone Snapshots: Ability to create, manage, and delete snapshots at Volume and Bucket levels
Ozone Quotas: The Ozone shell is the primary command line interface for managing the quota of volumes and buckets.
Container Balancer Threshold: You can now determine the threshold value before configuring the required parameters
Erasure Coding: The Ozone Erasure Coding feature provides data durability and fault-tolerance along with increased storage efficiency
SCM and OM decommissioning: Gracefully remove an OM/SCM from the SCM HA Ring.

For more information on the Ozone 7.1.9 features, see What's New in Ozone.

Zero Downtime Upgrades (ZDU)

Cloudera is reintroducing the concept of rolling upgrades in CDP 7.1.9 in an easier to use format called Zero Downtime Upgrades (ZDU). Zero Downtime Upgrades automates the process of performing rolling upgrades in an optimized format to allow for minimal to zero downtime depending on the services installed on a cluster. All future service packs and runtime upgrades will support ZDU. However, the enhancements brought by ZDU will be available on upgrades from CDP 7.1.7 and CDP 7.1.8. Before using this feature read the upgrade instructions. For more information, see the Zero Downtime upgrade documentation.

Upgrade CDP 7.1.7 SP2 to CDP 7.1.9

You can perform an In-place upgrade from CDP 7.1.7 SP2 to CDP 7.1.9. For more information, see CDP to CDP documentation.

Upgrade CDP 7.1.8 to CDP 7.1.9

You can perform an In-place upgrade from CDP 7.1.8 to CDP 7.1.9. For more information, see CDP to CDP documentation.

Upgrade CDP 7.1.7 SP1 to CDP 7.1.9

You can perform an In-place upgrade from CDP 7.1.7 SP1 to CDP 7.1.9. For more information, see CDP to CDP documentation.

Upgrade CDH 6 to CDP 7.1.9

You can perform In-place upgrade from CDH6 to CDP 7.1.9. For more information, see CDH 6 to CDP documentation.

Upgrade HDP 3 to CDP 7.1.9

You can perform In-place one-stage upgrade from HDP 3 to CDP 7.1.9 using CMA 2.6.2. For more information, see HDP 3 to CDP documentation.

Rollback CDP 7.1.9 to CDP 7.1.7 SP2

You can downgrade or rollback an upgrade from CDP Private Cloud Base 7 to CDP 7.1.7 SP2. The rollback restores your CDP cluster to the state it was in before the upgrade, including Kerberos and TLS/SSL configurations. For more information, see Rollback CDP 7.1.9 to CDP 7.1.7 SP2 documentation.

Rollback CDP 7.1.9 to CDP 7.1.8

You can downgrade or rollback an upgrade from CDP Private Cloud Base 7 to CDP 7.1.9. The rollback restores your CDP cluster to the state it was in before the upgrade, including the Kerberos and TLS/SSL configurations. For more information, see Rollback CDP 7.1.9 to CDP 7.1.8 documentation.

Rollback CDP 7.1.9 to CDH 6

You can downgrade or rollback an upgrade from CDP Private Cloud Base 7 to CDH 6. The rollback restores your CDH cluster to the state it was in before the upgrade, including the Kerberos and TLS/SSL configurations. For more information, see Rollback CDP 7.1.9 to CDH 6 documentation.

TLS 1.2 support for secured database connections

Certain CDP components, Cloudera Manager server, and Reports Manager support connections to backend databases that are secured with Transport Layer Security (TLS) 1.2 encryption. This enhances the security connections between CDP and backend databases, such as MySQL, PostgreSQL, MariaDB.

The following CDP components are supported:

Hive MetaStore
Hue
Schema Registry
Streams Messaging Manager
Oozie
Sqoop
Ranger
Ranger KMS

For more information on cluster services, see Configuring TLS 1.2 for cluster services

For more information on Cloudera Manager, see Configuring TLS 1.2 for Cloudera Manager

For more information on Reports Manager, see Configuring TLS 1.2 for Reports Manager.

TCPS support for connections to Oracle database

Certain CDP components support connections to backend Oracle database that are secured with Transmission Control Protocol with SSL (TCPS). This provides greater security for connections between CDP and the backend Oracle database. For more information, see TCPS support for connections to Oracle database.

The following CDP components are supported:

Hive MetaStore
Hue
Schema Registry
Streams Messaging Manager
Oozie
Sqoop
Ranger
Ranger KMS

Collecting Heartbeat data from Cloudera Manager

Beginning with Cloudera Manager 7.11.3, a report containing basic cluster information securely transmits to Cloudera periodically. This report contains cluster-related metadata to determine the version and size of each cluster. This information helps Cloudera to gain a clearer understanding of your deployments and deliver more robust support and ensure an improved customer experience.

Reports are saved locally for you with infrastructure isolated from the public internet. For assistance, open a General Administrative Assistance case on MyCloudera.

The generated report is human-readable for users and can be found under /var/lib/cloudera-scm-server/reports (configured as default).

Client RPMs

Client RPMs enable you to access services installed on the CDP cluster from your containerized application or edge nodes that are not managed by Cloudera Manager. You can use Client RPMs for the use cases that require thin client applications binding without having to download and install the entire CDP parcel which requires over 10 GB of storage space on each platform node. Starting with the CDP Private Cloud Base 7.1.9 release, '-client' RPM/Debian packages are available.

For more information, see Application Access

Support for noexec option on the /tmp directory

All Cloudera Runtime services, with the exception of Oozie and Sqoop, support the noexec option on the /tmp directory. The /tmp directory on Linux hosts is used by many applications to store non-persistent data and to execute transient scripts. Users require the noexec option on /tmp directory to eliminate possible security risks by preventing the execution of binaries from the /tmp filesystem. The noexec option prevents unintentional system modifications or corruption that may potentially lead to system instability or data theft.

Deprecation notices

For information, see Deprecation notices in Cloudera Runtime 7.1.9.