Known Issues in Apache Kudu

Known Issues identified in Cloudera Runtime 7.3.1.500 SP3:

There are no new known issues identified in this release.

There are no new known issues identified in this release.

There are no new known issues identified in this release.

There are no new known issues identified in this release.

There are no new known issues identified in this release.

Kudu supports both coarse-grain and fine-grain authorization, but Kudu does not yet support integration with Atlas.: None

KUDU-3619: Major delta compaction for a tablet might fail for particular workloads due to a bug introduced with KUDU-3367: 7.3.1.100; 7.3.1; A bug has been introduced with KUDU-3367 functionality. The bug manifests itself when a tablet server's maintenance thread attempts to run a major delta compaction on a tablet where many rows have been deleted, and the attempt fails with an error. To know more about the error message pattern, see KUDU-3619. If that happens, the corresponding tablet might accumulate a lot of updates that cannot be compacted and later garbage collected. In extreme cases, it could lead to running out of disk space when many tablet replicas hosted at the same tablet server hit the issue.; If a tablet server is affected by the issue, messages like the below are present in the tablet server's logs, where <tabletUUID> and <rowsetID> placeholders are populated with corresponding identifiers:; Major delta compaction failed on <tabletUUID>: Corruption: Failed major delta compaction on RowSet(<rowsetID>): No min key found: CFile base data in RowSet(<rowsetID>).; Set the --all_delete_op_delta_file_cnt_for_compaction flag to a very high value (e.g. 1000000) using the Tablet Server Advanced Configuration Snippet (Safety Valve) for gflagfile in the Cloudera Manager UI and restart all the tablet servers in the Kudu cluster.
Apache Jira: KUDU-3619.

Kudu HMS Sync is disabled and is not yet supported.