Fixed Issues in Kudu
Review the list of Kudu issues that are resolved in Cloudera Runtime 7.3.1
- KUDU-3576: Fix the Connection timeout After Tablet Server Restart
-
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
- 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
- Kudu now supports configuring a dedicated Spnego
keytab.
Apache Jira: KUDU-3496
- KUDU-3497: Optimize leader rebalancer algorithm
- Optimized the leader balancing algorithm to effectively handle corner cases detailed in the Jira.
- KUDU-3486: Clearing Tombstoned Replica Metadata During Heartbeat Processing in Kudu TServer
- The metadata of tombstoned replicas can occupy `kudu-tserver` memory and is now cleared during heartbeat processing.
