Cloudera Docs

Known issues in Cloudera Data Warehouse

Review the known issues and technical limitations for Cloudera Data Warehouse on cloud for service layer version 1.13.1-b44, Hive, Impala, Hue, and Iceberg runtime version 2026.0.21.4-12, and Trino runtime version 2026.0.24.0-37.

Known issues identified in the September 18, 2026 release

DWX-24242: Impala query socket timeout on Azure due to inactive LDAP connection drops
In this release, when running queries on an Impala Virtual Warehouse in Microsoft Azure, Azure Load Balancers can drop inactive LDAP connections without terminating the TCP session. Subsequent group lookups on these terminated connections can hang until the default Hadoop LDAP timeout of 60 seconds is reached, causing JDBC client queries to fail with a socket timeout error. 
[Cloudera][ImpalaJDBCDriver](500157) Socket timeout expired
.
Update the Impala coordinator core-site.xml configuration file by setting the hadoop.security.group.mapping.ldap.read.timeout.ms property to 5000 and the hadoop.security.group.mapping.ldap.connection.timeout.ms property to 3000 so dropped connections are quickly detected and retried.
Unable to copy the Trino JDBC URL from the Query Data modal
In this release, copying the JDBC URL for a Trino Virtual Warehouse from the Query Data modal copies an undefined value instead of the valid URL. This issue occurs when navigating through Overview > Query and Visualize Data > See More > Open Data Explorer and then clicking Copy JDBC URL after selecting a Trino Virtual Warehouse.
You can copy the JDBC URL by navigating to the Virtual Warehouses tab and selecting Details for the specific Virtual Warehouse.

Known issues identified before the September 18, 2026 release

DWX-23148: Environment deactivation might fail if EKS cluster update is in progress
When deactivating a Cloudera Data Warehouse environment on AWS, the operation might fail with an error indicating that the CloudFormation stack was unable to delete the EKS cluster due to an update in progress. This issue affects environments configured with both public and private executors. The failure is temporary and is typically resolved once the EKS cluster update is complete.
None
DWX-22295: Default Database Catalog or Hive Virtual Warehouse creation fails on Azure due to Istio validation webhook error
On Azure-based Cloudera Data Warehouse environments, default Database Catalog creation or Hive Virtual Warehouse deployment can intermittently fail during chart installation. The deployment driver is unable to install certain Helm charts such as, postgres-external, metastore, or Hive-related charts because calls to the Istio validation webhook (validation.istio.io on istiod.istio-system.svc:443) return a 500 Internal Server Error error. When this occurs, the affected Database Catalog or Hive Virtual Warehouse deployment enters an error state and does not become available for use. This behavior has only been observed on Azure and is linked to transient Istio networking issues.
None
DWX-20712: Environment diagnostic bundle collection failure
If you are collecting diagnostic bundles for AWS or Azure environments with a time range of more than 3 hours, the diagnostic bundle collection job fails. This issue is noticed if the data to be collected is greater than 5 GB.
None.
Known limitation: Cloudera Data Warehouse does not support S3 Express One Zone buckets
Cloudera recommends not deploying the Data Lake on S3 Express One Zone buckets. Cloudera Data Warehouse cannot read content present in the S3 Express One Zone buckets. The following limitations apply when using S3 Express buckets:
  • You can only use S3 Express buckets with Cloudera Data Hubs running Runtime 7.2.18 or higher versions. Currently, data services do not support S3 Express buckets.
  • S3 Express buckets are supported to use for logs and backups.
DWX-15144: Virtual Warehouse naming restrictions
You cannot create a Virtual Warehouse with the same name as an existing Virtual Warehouse even when the Virtual Warehouses are in different environments. Conversely, Database Catalogs support duplicate names across different environments.
None.
AWS availability zone inventory issue
In this release, you can select a preferred availability zone when you create a Virtual Warehouse; however, AWS might not be able to provide enough compute instances of the type that Cloudera Data Warehouse needs.
If you experience this AWS issue, try recreating the Virtual Warehouse with a different availability zone.
Incorrect diagnostic bundle location
When you create a Virtual Warehouse, collect a diagnostic bundle of log files for troubleshooting, and click Edit > Diagnostic Bundle, the displayed file path to the diagnostic bundle is incorrect. The path is missing your storage account name.
To find your diagnostic bundle, add your storage account name to the beginning of the path, for example: 
my-storage-account-name/log-files/clusters/my-env/my-warehouse-xx-yy/warehouse/debug-artifacts/hive/compute-zz-mvvf/compute-zz-mvvf-0926210111-0927090111-01234.zip
If you do not know your storage account name, locate it in the Cloudera Management Console by performing the following steps:
  1. Click Environments and select your environment name.
  2. Scroll down to the Logs Storage and Audits section.
  3. Copy the storage account name listed as the first part of the path.