Known Issues in Kudu

Known issues identified in Cloudera Runtime 7.1.9 SP1 CHF 13

CDPD-94474: Kudu Tablet Server Crash on RHEL9

Kudu tablet servers kudu-tserver crash on Red Hat Enterprise Linux 9 (RHEL9) x86_64 platforms when the libgcc package is updated to version 11.5.0-11 or newer. This crash manifests as a Segmentation Fault (SIGSEGV) or an Abort (SIGABRT) error under certain workloads.

1. Log in to Cloudera Manager as an Administrator.
2. Navigate to Cloudera Manager > Clusters > Kudu > Configuration.
3. Navigate to the Configuration tab, and add the following value in the Tablet Server Advanced Configuration Snippet (Safety Valve) for gflagfile for the Tablet Server Default Group field:

   --mrs_use_codegen=false

4. Click Save Changes.
5. Restart the Kudu Service.

Known issues identified before Cloudera Runtime 7.1.9 SP1 CHF 13

You get "The user 'kudu' is not part of group 'hive' on the following hosts:" warning by the Host Inspector.

If you are using fine-grained authorization for Kudu, and you are also using Kudu-HMS integration with HDFS-Sentry sync, then you may get the "The user 'kudu' is not part of group 'hive' on the following hosts:" warning while upgrading.

Workaround: Run the following command on all the HMS servers:

usermod -aG hive kudu

Cloudera upgraded the HSQLDB dependency from 1.8.0.10 to 2.7.1 and this causes incompatibility issues in Sqoop jobs that are stored in HSQLDB.

Run the following command on all the HMS servers:

usermod -aG hive kudu

Unsupported features

Kudu HMS Sync is disabled and is not yet supported