Cloudera Docs

Fixed Issues in Kudu

Review the list of Kudu issues that are resolved in Cloudera Runtime 7.3.1, its service packs and cumulative hotfixes.

Cloudera Runtime 7.3.1.706 SP3 CHF 2

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.600 SP3 CHF 1

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.500 SP3

CDPD-85458: Prometheus Metrics Enhancement for Kudu
7.3.1.500
Kudu now includes Prometheus metrics by adding tablet-level metrics alongside the existing server-level metrics. This improvement provides you with deeper insights to more effectively diagnose performance issues in busy clusters containing up to 2,000 tablets.
Apache Jira:KUDU-3563.

Cloudera Runtime 7.3.1.400 SP2

CDPD-82273: Backport KUDU-3661 Ranger policy not honored in Kudu
7.3.1.400
Fixed an issue in the Ranger authorization provider that could cause some table privileges to be missing in certain environments. This happened when processing the SELECT privilege, which caused the system to stop checking for additional permissions. The issue was primarily seen on RHEL/CentOS 8 systems due to platform-specific behavior in the underlying system libraries.
CDPD-82275: Run a range-aware cluster rebalance with multiple tables
Previously, when rebalancing a cluster with the Kudu command-line tool, the --enable_range_rebalancing flag required the --tables flag to specify exactly one table. This fix removes that restriction. You can now pass multiple tables to the --tables flag when range rebalancing is enabled. Range-partitioned tables among those specified will be rebalanced with ranges considered, while other tables rebalance as usual. If you do not set the --tables flag, all tables in the cluster will be rebalanced.
CDPD-81231: Backport KUDU-3638, disable KUDU-3486 behavior by default
This fix addresses an issue with tombstoned tablets caused by functionality introduced in KUDU-3486. The fix disables this functionality. To re-enable the behavior, adjust the --tserver_send_tombstoned_tablets_report_interval_secs flag as needed.
CDPD-81229: Backport KUDU-3647 more robust zlib wrapper code
7.3.1.400
This fix improves robust error handling for the utility wrappers zlib::{CompressLevel, Uncompress}(). It also resolves a data corruption issue in Base64Decode(), where trailing bytes encoded as 'A' were previously discarded.
CDPD-81234: Backport KUDU CVE fixes
7.3.1.400
This fix addresses recently identified security vulnerabilities. The following third-party components have been upgraded:
  • protobuf: Upgraded to address CVE-2022-3171.
  • zlib: Upgraded to address CVE-2022-37434.
  • curl: Upgraded to address CVE-2024-11053.

Resolved a long-standing bug by fixing a race condition within the OpDriver. This fix improves stability and ensures the expected behavior of the driver.

Cloudera Runtime 7.3.1.300 SP1 CHF 1

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.200 SP1

There are no fixed issues in this release.

Cloudera Runtime 7.3.1.100 CHF 1

CDPD-78316: Disable KUDU-3367 behavior by default
This fix addresses an issue with major delta compaction caused by functionality introduced in KUDU-3367. The fix disables the functionality by adjusting the default value of the -all_delete_op_delta_file_cnt_for_compaction flag. While the original functionality was intended to optimize Kudu deployments of early versions, the functionality introduced by KUDU-3367 isn't relevant for data generated by Kudu servers in Cloudera Base on premises 7.1.1 and newer versions.

Apache Jira: KUDU-3619.

Cloudera Runtime 7.3.1

KUDU-3576: Fix the Connection timeout After Tablet Server Restart
7.3.1

In Kudu, if a Java client application maintains an open connection to a tablet server and the tablet server is restarted or encounters a network error, the client cannot re-establish communication with the tablet server even after it comes back online. The fix resolves the issue by updating the Kudu Java client.

Apache Jira: KUDU-3576

KUDU-3577: Fix the altering tables with custom hash schemas
7.3.1
This fix resolves the issue caused by the design defect related to partition boundaries for ranges with custom hash schemas, which requires re-encoding the information as a part of PartitionSchemaPB stored in the system catalog upon particular modifications of the table’s schema. A proper solution would be using the primary-key-only projection of a table's schema to encode the information on range boundaries while also maintaining backward compatibility with already-released Kudu clients.

Apache Jira: KUDU-3577

KUDU-3496: Support for SPNEGO dedicated keytab
7.3.1
Kudu now supports configuring a dedicated Spnego keytab.

Apache Jira: KUDU-3496

KUDU-3497: Optimize leader rebalancer algorithm
7.3.1
Optimized the leader balancing algorithm to effectively handle corner cases detailed in the Jira.

Apache Jira: KUDU-3497

KUDU-3486: Clearing Tombstoned Replica Metadata During Heartbeat Processing in Kudu TServer
7.3.1
The metadata of tombstoned replicas can occupy `kudu-tserver` memory and is now cleared during heartbeat processing.

Apache Jira: KUDU-3486