Scheduling executor pods on dedicated worker nodes in Cloudera Data Warehouse on premises
To optimize resource utilization on your cluster and improve query performance, Cloudera Data Warehouse allows you to schedule Hive and Impala executor and coordinator pods on dedicated executor nodes that are tainted for Cloudera Data Warehouse and equipped with more local storage, either using SSDs or NVMEs.
Nodes that have local storage are prioritized for Cloudera Data Warehouse query executor pods, preventing their use by other Cloudera Data Warehouse or data service pods. By default, the Use dedicated nodes for executors option is disabled. When you enable this option, Hive and Impala executor and coordinator pods can only be scheduled on the labeled worker nodes. Make sure you label these nodes in advance.
This task describes how to enable the Use dedicated executor node option on an existing environment:
On Cloudera Embedded Container Service, you must dedicate the Cloudera Embedded Container Service cluster nodes for specific workloads using Cloudera Manager, as described in the Dedicating ECS nodes for specific workloads section.
On OpenShift Container Platform (OCP), you must dedicate the OCP cluster nodes for specific workloads using the kubectl taint command, as described in the Dedicate an SSD node for Cloudera Data Warehouse workloads section.
- Log in to the Cloudera Data Warehouse service as a DWAdmin.
- On the left navigation pane, go to .
- In Advanced Configuration, select Use dedicated executor node checkbox.
- Click the Update button.
