General known issues
This topic describes the general service-wide known issues for Cloudera Data Warehouse (CDW) Private Cloud.
Known issues identified in 1.5.3
- DWX-17880: Hive Virtual Warehouse does not start if the bind user contains special characters
- The Hive virtual warehouse may fail to start up if you have
specified the following special characters in the LDAP bind credential password:
< > & ' "
. This happens because the HiveServer2 (HS2) pod gets stuck in the CrashLoopBackOff state with the following error in its logs: error parsing conf file:/etc/hive/conf/hive-site.xml com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '&' (code 38) in content after '<' (malformed start element?). at [row,col,system-id]: [388,13,"file:/etc/hive/conf/hive-site.xml"].
Known issues identified in 1.5.2
- VIZ-2269: Issue with impersonation in CDW Impala connections
- You may see the following error while creating or editing the data connection to a CDW Impala or Hive Virtual Warehouse and using the connection details auto-populated from the CDW Warehouse drop-down: User <username> is not authorized to delegate to <username>. This happens because the Impersonation and Trusted Impersonation options are both enabled. This affects CDV 7.1.6.
Known issues identified in 1.5.1
- DWX-15142 Character restriction on environment name when using FreeIPA server version 4.9.8 and higher
- FreeIPA is supported as an authentication mechanism starting with the 1.5.1 release. If you are using FreeIPA version 4.9.8 and higher, then note that the host names are limited to 64 characters. Because the environment name is part of the host name, the environment name must not exceed 17 characters.
Known issues identified in 1.5.0
- DWX-18903: Service "postgres-service-default-warehouse" is invalid: spec.externalName error
- You see the following error during the Database Catalog creation
stage after activating the environment in CDW:
Service "postgres-service-default-warehouse" is invalid: spec.externalName a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
. This could happen because if the value of the Hive Metastore Database Host (hive_metastore_database_host) property on the base cluster is not specified in lowercase.
Known issues identified before 1.4.1
- DWX-10403: Executor pods get stuck in pending state with a warning
- In rare circumstances, when Impala or Hive executors start up either due to autoscaling or by manually restarting the executors, the pods may get stuck in a pending state with a warning such as "volume node affinity conflict". This happens due to a race condition in the storage class that provides local volumes.
- DWX-8502: HMS health check does not check port 9083
- The HMS health check script does not check the health of its service port 9083 and may provide incorrect health status.