Known issues in Impala Virtual Warehouses

Known issues identified in 1.5.5

DWX-21021: Impala virtual warehouses does not function after host reboot: After a host restarts, Impala components struggle to resume operations on the same node if the cluster has limited resources. This happens because these components are tied to specific local storage. If other small pods occupy that storage first, Impala's main processing units get stuck and cannot start.; Rebuild the affected virtual warehouses. See, Rebuilding a Virtual Warehouse
DWX-21147: Virtual Warehouse Creation Fails Intermittently After Upgrade: After upgrading from version Cloudera Data Warehouse on premises 1.5.4 CHF3 to 1.5.5, the first attempt to create or update an Impala Virtual Warehouse might fail. This occurs due to an internal timing conflict during resource pool migration.; Retry the Virtual Warehouse creation or update.

DWX-18505: Resource template changes back to Reduced resources while creating a Virtual Warehouse: On the Create Virtual Warehouse modal, suppose you selected Default resources from the Resource Template drop-down menu. When you wait for a few seconds or click elsewhere on the modal, you see that the resource template changes back to Reduced resources. However, when you create the Virtual Warehouse, the Virtual Warehouse is created with the resource template you initially selected. This is a Cloudera Data Warehouse UI defect you encounter on environments that are activated using the low resource mode.; None.
DWX-18445: Virtual Warehouses get stuck in the deleting state: You may intermittently notice that a Virtual Warehouses gets stuck in the deleting state when you delete a Virtual Warehouse in Cloudera Data Warehouse. This could be due to a failing diagnostic job that is in an Init:0/1 state in the namespace.; None. The diagnostic job gets cleaned up in one hour, after which the Virtual Warehouse gets deleted successfully.

DWX-14292: Impala executors and coordinator pods get stuck in pending state: If you have enabled low resource mode while activating an environment in Cloudera Data Warehouse and also enabled the option to customize pod sizes for Impala from the Advanced Settings page, then you may notice that the executors and coordinator pods do not request the set amount of memory and CPU. This happens because the low resource mode overrides the default pod configuration.; Low resource mode and custom pod configurations for Impala cannot be used at the same time. To resolve this issue, do not select the Low resource mode option while activating an environment. Instead, create custom pod configurations with lower resources for Impala. You can continue to use lesser resources as defined in the custom pod configuration for Hive.